Fetch documents

When to use this

Use GET /external/v1/encounters/{encounter_id}/documents/{document_id} after selecting a document from an encounter response or an approved webhook follow-up.

This route returns one supported clinical document for the same caller organization as the encounter. A schema_type of document returns clinical markdown content; a schema_type of ambient_transcript returns transcript metadata only.

Required scopes

The caller organization must also be enabled for document routes.

Request

curl "https://api.example.test/external/v1/encounters/enc_9YpJvK2/documents/doc_Note1" \
  -H "Authorization: Bearer ch_sk_example_123"

Document detail does not accept query parameters. Authorized callers receive unsupported_filter for any query key on this route.

Response

{
  "document": {
    "document_id": "doc_Note1",
    "encounter_id": "enc_9YpJvK2",
    "schema_type": "document",
    "title": "Progress note",
    "status": null,
    "workflow_variant": null,
    "created_at": "2026-05-25T14:30:00Z",
    "updated_at": "2026-05-25T15:00:00Z",
    "content": {
      "format": "markdown",
      "text": "Assessment and plan text."
    }
  }
}

For an ambient transcript document, this route returns metadata. Use the transcript route for speaker turns and timing, and the audio route for a short-lived audio URL when available.

Common errors

Path IDs are opaque ChartHero IDs. Treat example IDs as illustrative strings only.

Next step

For ambient transcript documents, continue to Fetch transcript and audio. See GET /external/v1/encounters/{encounter_id}/documents/{document_id} in the API Reference for the generated endpoint contract.