> ## Documentation Index > Fetch the complete documentation index at: https://docs.stardex.com/llms.txt > Use this file to discover all available pages before exploring further. # Get meeting recording by ID > Retrieve detailed information about a specific meeting recording including the associated calendar meeting details and full transcript text. The `transcript_text` field is always included. It will be null if the recording has not finished processing or no transcript was generated. ## OpenAPI ````yaml /api-reference/openapi-v1.json get /v1/meeting-recordings/{id} openapi: 3.1.0 info: title: Stardex API (v1) version: 1.0.0 description: >- Stardex ATS API — manage candidates, jobs, companies, and recruiting workflows. servers: - url: https://api.stardex.ai description: Production API server security: - bearerAuth: [] tags: - name: Persons description: Manage person records — contacts, work history, and custom fields. - name: Jobs description: Manage job postings — pipeline stages, team members, and custom fields. - name: Candidates description: Manage candidate records and pipeline stage transitions. - name: Companies description: Browse and retrieve company records. - name: Lists description: Create, search, and retrieve saved person and company lists. - name: Person Activities description: Create and manage activity records (notes, emails, meetings) for persons. - name: Team Members description: List team members for use in search filters and assignments. - name: Custom Fields description: Retrieve custom field definitions and tag options for search filters. paths: /v1/meeting-recordings/{id}: get: tags: - Meeting Recordings summary: Get meeting recording by ID description: >- Retrieve detailed information about a specific meeting recording including the associated calendar meeting details and full transcript text. The `transcript_text` field is always included. It will be null if the recording has not finished processing or no transcript was generated. operationId: getMeetingRecordingById parameters: - in: path name: id required: true schema: type: string description: Meeting recording UUID responses: '200': description: Meeting recording fetched content: application/json: schema: $ref: '#/components/schemas/MeetingRecordingByIdResponse' example: success: true data: id: 5c6d7e8f-9012-3456-7890-abcdef012345 calendar_meeting_id: 6d7e8f90-1234-5678-9012-abcdef012345 calendar_meeting: id: 6d7e8f90-1234-5678-9012-abcdef012345 meeting_title: Weekly Engineering Sync meeting_url: https://meet.google.com/abc-defg-hij start_time: '2026-04-07T10:00:00.000Z' meeting_started_at: '2026-04-07T10:00:00.000Z' meeting_ended_at: '2026-04-07T11:00:00.000Z' recording_duration_seconds: 3600 processing_status: completed transcript_text: |- Speaker 1: Good morning everyone... Speaker 2: Hi, thanks for joining... summary_text: |- Summary - Discussed Q2 roadmap and deliverables. - Agreed on hiring 2 senior engineers by May. Next Steps - Pranav to draft the JD. created_at: '2026-04-07T11:05:00.000Z' updated_at: '2026-04-07T11:10:00.000Z' '400': description: Validation error content: application/json: schema: type: object properties: success: type: boolean enum: - false description: Always false for error responses. error: type: object properties: code: type: string description: >- Machine-readable error code (e.g. "VALIDATION_ERROR", "NOT_FOUND"). message: type: string description: Human-readable error description. required: - code - message required: - success - error '404': description: Resource not found content: application/json: schema: type: object properties: success: type: boolean enum: - false description: Always false for error responses. error: type: object properties: code: type: string description: >- Machine-readable error code (e.g. "VALIDATION_ERROR", "NOT_FOUND"). message: type: string description: Human-readable error description. required: - code - message required: - success - error '500': description: Internal server error content: application/json: schema: type: object properties: success: type: boolean enum: - false description: Always false for error responses. error: type: object properties: code: type: string description: >- Machine-readable error code (e.g. "VALIDATION_ERROR", "NOT_FOUND"). message: type: string description: Human-readable error description. required: - code - message required: - success - error components: schemas: MeetingRecordingByIdResponse: type: object properties: success: type: boolean enum: - true data: $ref: '#/components/schemas/MeetingRecordingDetail' required: - success - data MeetingRecordingDetail: type: object properties: id: type: string description: Meeting recording UUID. calendar_meeting_id: type: - string - 'null' description: Associated calendar meeting UUID. calendar_meeting: type: - object - 'null' properties: id: type: string description: Calendar meeting UUID. meeting_title: type: - string - 'null' description: Meeting title. meeting_url: type: string description: Meeting URL (e.g. Zoom/Google Meet link). start_time: type: string description: Meeting start time (ISO 8601). required: - id - meeting_title - meeting_url - start_time description: Calendar meeting details (always included when available). meeting_started_at: type: - string - 'null' description: When the meeting started (ISO 8601). meeting_ended_at: type: - string - 'null' description: When the meeting ended (ISO 8601). recording_duration_seconds: type: - number - 'null' description: Duration of the recording in seconds. processing_status: type: - string - 'null' description: 'Processing status: pending, processing, completed, or failed.' transcript_text: type: - string - 'null' description: >- Full transcript text. Null when no transcript is available (e.g. recording still processing). summary_text: type: - string - 'null' description: >- Plain-text AI-generated summary of the meeting. Null when no summary has been generated yet. Prefer this over `transcript_text` for high-level recap. created_at: type: string description: ISO 8601 creation timestamp. updated_at: type: string description: ISO 8601 last update timestamp. required: - id - calendar_meeting_id - calendar_meeting - meeting_started_at - meeting_ended_at - recording_duration_seconds - processing_status - transcript_text - summary_text - created_at - updated_at securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: JWT description: >- Authenticate with a Bearer token: API key, OAuth token, or session token. ````