> ## Documentation Index > Fetch the complete documentation index at: https://docs.telepatia.ai/llms.txt > Use this file to discover all available pages before exploring further. # List a patient's scribe sessions > List the scribe sessions for a patient, paginated. The patient id can be the public id (sp_...) or the internalCode you set for your institution. ## OpenAPI ````yaml /scribe-api/openapi.json get /v1/patients/{patient_id}/scribe-sessions openapi: 3.1.0 info: title: Scribe Public API description: >- External-facing REST API for integrating with the Telepatia platform. Authenticate with API keys, set consultation context, and look up scribe sessions. version: 0.1.0 servers: - url: https://scribe-api.telepatia.ai description: Production security: - BearerAuth: [] paths: /v1/patients/{patient_id}/scribe-sessions: get: tags: - Patients summary: List a patient's scribe sessions description: >- List the scribe sessions for a patient, paginated. The patient id can be the public id (sp_...) or the internalCode you set for your institution. operationId: >- api_patient_scribe_sessions_list_v1_patients__patient_id__scribe_sessions_get parameters: - name: patient_id in: path required: true schema: type: string title: Patient Id - name: page in: query required: false schema: type: integer minimum: 1 description: Page number (1-based). default: 1 title: Page description: Page number (1-based). - name: limit in: query required: false schema: type: integer maximum: 50 minimum: 1 description: Number of items per page. default: 20 title: Limit description: Number of items per page. responses: '200': description: Successful Response content: application/json: schema: $ref: '#/components/schemas/PatientSessionListResponse' example: hasMore: false items: - completedAt: '2026-02-20T10:30:00Z' consultationInternalId: CONSULT-12345 createdAt: '2026-02-20T10:00:00Z' id: ss_a1b2c3d4e5f6g7h8 patientName: John Doe scribeSessionModality: IN_PERSON specialty: Cardiology status: completed limit: 20 page: 1 total: 1 totalPages: 1 '400': description: >- Bad Request — invalid parameters, validation failures, or missing fields. content: application/json: examples: parameter_missing: summary: Missing required field value: error: type: invalid_request_error code: parameter_missing message: name is required. param: name requestId: 3f9a1c2e-5b7d-4a21-9f0c-8e6d4b2a1c30 parameter_invalid: summary: Invalid field value value: error: type: invalid_request_error code: parameter_invalid message: >- idCountry must be a valid country name, ISO alpha-2, or ISO alpha-3 code. param: idCountry requestId: 3f9a1c2e-5b7d-4a21-9f0c-8e6d4b2a1c30 account_invalid: summary: Invalid account value: error: type: invalid_request_error code: account_invalid message: Account has no valid authId. requestId: 3f9a1c2e-5b7d-4a21-9f0c-8e6d4b2a1c30 schema: $ref: '#/components/schemas/ErrorResponse' '401': description: Unauthorized — missing or invalid API key. content: application/json: examples: authentication_required: summary: Invalid or missing API key value: error: type: authentication_error code: authentication_required message: Invalid API key. requestId: 3f9a1c2e-5b7d-4a21-9f0c-8e6d4b2a1c30 schema: $ref: '#/components/schemas/ErrorResponse' '404': description: Not Found — the requested resource does not exist. content: application/json: examples: resource_not_found: summary: Resource not found value: error: type: invalid_request_error code: resource_not_found message: No session scribe found for the given consultation ID. requestId: 3f9a1c2e-5b7d-4a21-9f0c-8e6d4b2a1c30 schema: $ref: '#/components/schemas/ErrorResponse' '503': description: Service Unavailable — an external dependency is down. content: application/json: examples: service_unavailable: summary: External service unavailable value: error: type: api_error code: service_unavailable message: >- The service is temporarily unavailable. Please try again later. requestId: 3f9a1c2e-5b7d-4a21-9f0c-8e6d4b2a1c30 schema: $ref: '#/components/schemas/ErrorResponse' security: - BearerAuth: [] components: schemas: PatientSessionListResponse: properties: items: items: $ref: '#/components/schemas/PatientSessionItem' type: array title: Items description: Page of scribe sessions. total: type: integer title: Total description: Total sessions for the patient in the caller's scope. page: type: integer title: Page description: Current page number (1-based). limit: type: integer title: Limit description: Number of items per page. totalPages: type: integer title: Totalpages description: Total number of pages. hasMore: type: boolean title: Hasmore description: Whether another page exists. type: object required: - items - total - page - limit - totalPages - hasMore title: PatientSessionListResponse description: Paginated list of a patient's scribe sessions. examples: - hasMore: false items: - completedAt: '2026-02-20T10:30:00Z' consultationInternalId: CONSULT-12345 createdAt: '2026-02-20T10:00:00Z' id: ss_a1b2c3d4e5f6g7h8 patientName: John Doe scribeSessionModality: IN_PERSON specialty: Cardiology status: completed limit: 20 page: 1 total: 1 totalPages: 1 ErrorResponse: description: Standardized error response envelope. properties: error: $ref: '#/components/schemas/ErrorDetailWithRequestId' required: - error title: ErrorResponse type: object PatientSessionItem: properties: id: type: string maxLength: 255 title: Id examples: - ss_a1b2c3d4e5f6g7h8 status: type: string maxLength: 255 title: Status examples: - completed createdAt: anyOf: - type: string format: date-time - type: 'null' title: Createdat completedAt: anyOf: - type: string format: date-time - type: 'null' title: Completedat patientName: anyOf: - type: string maxLength: 255 - type: 'null' title: Patientname scribeSessionModality: anyOf: - type: string - type: 'null' title: Scribesessionmodality description: >- The modality of the scribe session (e.g. 'IN_PERSON', 'TELEMEDICINE'). consultationInternalId: anyOf: - type: string - type: 'null' title: Consultationinternalid description: The consultation ID provided by the API consumer. specialty: anyOf: - type: string - type: 'null' title: Specialty description: The medical specialty of the clinician who conducted the session. type: object required: - id - status title: PatientSessionItem description: >- A single scribe session in a patient's timeline. Mirrors the single-session lookup response — lifecycle + consultation metadata only. ErrorDetailWithRequestId: description: >- Top-level error object: :class:`ErrorDetail` plus the request correlation id. Kept as a subclass rather than a field on ``ErrorDetail`` because ``ErrorDetail`` is also the per-item error shape inside the batch account-creation response (``BatchAccountResult.error``), which is serialized with nulls included. Adding the field there would publish ``"requestId": null`` on an HTTP 200, and there is only ever one request id per batch anyway -- batch callers read the ``X-Request-ID`` response header. properties: type: description: Broad error category for high-level handling. examples: - invalid_request_error title: Type type: string code: description: Machine-readable error code. Clients should switch on this value. examples: - parameter_invalid title: Code type: string message: description: Human-readable error message ending with a period. examples: - >- idCountry must be a valid country name, ISO alpha-2, or ISO alpha-3 code. title: Message type: string param: anyOf: - type: string - type: 'null' default: null description: The request field that caused the error, if applicable. examples: - idCountry title: Param details: anyOf: - additionalProperties: true type: object - type: 'null' default: null description: Optional structured, machine-readable context for the error. examples: - pendingConsultations: - sessionId: abc123 url: https://... title: Details requestId: anyOf: - type: string - type: 'null' default: null description: >- Unique id for this request, identical to the X-Request-ID response header. Quote it when contacting support. examples: - 3f9a1c2e-5b7d-4a21-9f0c-8e6d4b2a1c30 title: Requestid required: - type - code - message title: ErrorDetailWithRequestId type: object securitySchemes: BearerAuth: type: http scheme: bearer description: API key passed as a Bearer token ````