> ## 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. # Get an appointment by id > Get one appointment by its public id (apt_...) or the consultationInternalId you sent when creating it. Returns 404 if no appointment with that id is visible to your key. ## OpenAPI ````yaml /scribe-api/openapi.json get /v1/appointments/{appointment_id} 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/appointments/{appointment_id}: get: tags: - Appointments summary: Get an appointment by id description: >- Get one appointment by its public id (apt_...) or the consultationInternalId you sent when creating it. Returns 404 if no appointment with that id is visible to your key. operationId: api_appointment_get_v1_appointments__appointment_id__get parameters: - name: appointment_id in: path required: true schema: type: string title: Appointment Id responses: '200': description: Successful Response content: application/json: schema: $ref: '#/components/schemas/AppointmentResponse' example: appointmentType: follow-up consultationInternalId: CONSULT-12345 createdAt: '2026-08-28T12:00:00.000Z' end: '2026-09-01T14:30:00.000Z' id: apt_a1b2c3d4e5f6g7h8 minutesDuration: 30 reason: Follow-up serviceType: cardiology start: '2026-09-01T14:00:00.000Z' status: booked '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: AppointmentResponse: properties: id: type: string title: Id description: Stable public identifier. examples: - apt_a1b2c3d4e5f6g7h8 consultationInternalId: anyOf: - type: string - type: 'null' title: Consultationinternalid examples: - CONSULT-12345 status: type: string title: Status examples: - booked start: anyOf: - type: string - type: 'null' title: Start examples: - '2026-09-01T14:00:00.000Z' end: anyOf: - type: string - type: 'null' title: End examples: - '2026-09-01T14:30:00.000Z' minutesDuration: anyOf: - type: integer - type: 'null' title: Minutesduration examples: - 30 serviceType: anyOf: - type: string - type: 'null' title: Servicetype examples: - cardiology appointmentType: anyOf: - type: string - type: 'null' title: Appointmenttype examples: - follow-up reason: anyOf: - type: string - type: 'null' title: Reason examples: - Follow-up description: anyOf: - type: string - type: 'null' title: Description examples: - Routine check createdAt: type: string title: Createdat description: ISO-8601 timestamp when the appointment was created. type: object required: - id - status - createdAt title: AppointmentResponse description: A single appointment. `id` is the stable public id (apt_...). examples: - appointmentType: follow-up consultationInternalId: CONSULT-12345 createdAt: '2026-08-28T12:00:00.000Z' end: '2026-09-01T14:30:00.000Z' id: apt_a1b2c3d4e5f6g7h8 minutesDuration: 30 reason: Follow-up serviceType: cardiology start: '2026-09-01T14:00:00.000Z' status: booked ErrorResponse: description: Standardized error response envelope. properties: error: $ref: '#/components/schemas/ErrorDetailWithRequestId' required: - error title: ErrorResponse type: object 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 ````