> ## Documentation Index > Fetch the complete documentation index at: https://docs.arrays.org/llms.txt > Use this file to discover all available pages before exploring further. # Get one event transcript's full text > [OpenAPI JSON Spec](/docs/output/v1_stocks_event-transcripts_event-id_get.json) Retrieve the full transcript text for one event by event_id, across all 6 FactSet event types. Body sections/content use the same parser as GET /stocks/earnings-transcript, so the shape is identical field-for-field. **Multiple listed entities per event**: a small number of events (e.g. dual share classes, cross-listings, M&A calls) are associated with more than one symbol. This endpoint takes only `event_id` — there is no `symbol` disambiguation parameter — and returns exactly one row in that case, chosen by the highest row_version. The transcript text is identical across such rows; only the `symbol` field differs. Use the list endpoint (filtered by symbol) if you need to know every symbol an event is associated with. **Response Data Structure** - `data` ([]EventTranscript): always a single-element array (never a bare object) on success, containing `transcript`. - `fiscal_year` / `fiscal_quarter` are `null` (not omitted, not `""`) unless event_type is Earnings. - `metadata.data_as_of`: this row's ingestion time (unix seconds). ## OpenAPI ````yaml /api-reference/openapi.json get /v1/stocks/event-transcripts/{event_id} openapi: 3.0.0 info: contact: {} description: >- Welcome to Arrays! Arrays is a unified financial data layer for both financial institutions and retail users, delivering comprehensive market data across crypto and equity markets. Our datasets cover fundamentals, ETFs, options, crypto, and more. Visit [arrays.org](https://arrays.org) to request an API key and start your free trial. You can explore our full API offerings in the documentation below. For any questions regarding APIs or pricing, please contact support@arrays.org. title: Arrays API version: '1.0' servers: - url: https://data-tools.prd.arrays.org/api security: [] paths: /v1/stocks/event-transcripts/{event_id}: get: tags: - Stock summary: Get one event transcript's full text description: >- [OpenAPI JSON Spec](/docs/output/v1_stocks_event-transcripts_event-id_get.json) Retrieve the full transcript text for one event by event_id, across all 6 FactSet event types. Body sections/content use the same parser as GET /stocks/earnings-transcript, so the shape is identical field-for-field. **Multiple listed entities per event**: a small number of events (e.g. dual share classes, cross-listings, M&A calls) are associated with more than one symbol. This endpoint takes only `event_id` — there is no `symbol` disambiguation parameter — and returns exactly one row in that case, chosen by the highest row_version. The transcript text is identical across such rows; only the `symbol` field differs. Use the list endpoint (filtered by symbol) if you need to know every symbol an event is associated with. **Response Data Structure** - `data` ([]EventTranscript): always a single-element array (never a bare object) on success, containing `transcript`. - `fiscal_year` / `fiscal_quarter` are `null` (not omitted, not `""`) unless event_type is Earnings. - `metadata.data_as_of`: this row's ingestion time (unix seconds). parameters: - description: Numeric event ID in: path name: event_id required: true schema: type: string responses: '200': description: Successfully retrieved the event transcript content: application/json: schema: allOf: - $ref: '#/components/schemas/model.APIResponse' - properties: data: items: $ref: '#/components/schemas/model.EventTranscript' type: array type: object '400': description: Invalid event_id, or no event transcript found content: application/json: schema: allOf: - $ref: '#/components/schemas/model.APIResponse' - properties: data: $ref: '#/components/schemas/model.APIError' type: object '500': description: Internal server error content: application/json: schema: allOf: - $ref: '#/components/schemas/model.APIResponse' - properties: data: $ref: '#/components/schemas/model.APIError' type: object security: - ApiKeyAuth: [] components: schemas: model.APIResponse: properties: data: {} error: $ref: '#/components/schemas/model.APIError' metadata: {} pagination: {} request_id: type: string success: type: boolean type: object model.EventTranscript: properties: event_date: description: >- EventDate is the event's calendar date (YYYY-MM-DD, UTC); "" if unknown. type: string event_datetime: description: >- EventDatetime is the meeting's actual start moment, as an RFC3339 UTC timestamp; "" if unknown. type: string event_id: type: string event_type: type: string fiscal_quarter: type: string fiscal_year: description: >- FiscalYear / FiscalQuarter are non-nil ONLY for Earnings events: a non-Earnings event has no fiscal-period concept at all (not merely an empty one), so these serialize as JSON null — deliberately no `omitempty` — rather than being omitted or emitted as "". type: string headline: type: string published_at: description: >- PublishedAt is the transcript publication moment (story_date_time), as an RFC3339 UTC timestamp; "" if unknown. type: string symbol: type: string transcript: description: >- Transcript is populated only by the detail endpoint; the list endpoint leaves it nil so `omitempty` drops the key entirely (design doc §6.2: list responses never carry the transcript body). items: $ref: '#/components/schemas/model.SectionEntry' type: array type: object model.APIError: properties: code: example: RESOURCE_NOT_FOUND type: string details: items: $ref: '#/components/schemas/model.APIErrorDetail' type: array docs_url: type: string examples: items: type: string type: array hint: type: string message: example: The requested resource was not found. type: string suggestions: items: type: string type: array type: object model.SectionEntry: properties: content: items: $ref: '#/components/schemas/model.TranscriptEntry' type: array section: type: string type: object model.APIErrorDetail: properties: field: type: string got: type: string reason: type: string type: object model.TranscriptEntry: properties: content: type: string speaker: type: string title: type: string type: object securitySchemes: ApiKeyAuth: description: 'API Key authentication. Example: "your-api-key-here"' in: header name: X-API-Key type: apiKey ````