> ## Documentation Index > Fetch the complete documentation index at: https://docs.ringg.ai/llms.txt > Use this file to discover all available pages before exploring further. # Get Call Details > Retrieves detailed information about a specific call using its unique identifier. Use the send_analysis parameter to include analysis data in the response. Fetch a detailed record for one call. Use this when a user opens a call detail view or when support needs the full context for a specific `call_id`. ## When to use * Show transcript, recording, status, and metadata for one call. * Debug a failed or unexpected call. * Fetch analysis for a call after receiving a webhook event. ## Integration notes * Pass the unique call ID as the `id` query parameter. * Use `send_analysis=true` only when the caller needs analysis data; this keeps lightweight detail views faster. * Store the `call_id` returned by call initiation and webhook payloads. * The returned recording URL is valid for 24 hours after the call. Download and store the recording within that window if you need to retain it. ## OpenAPI ````yaml get /calling/call-details openapi: 3.0.0 info: title: Ringg AI API Documentation description: >- This is the documentation for the Ringg AI APIs. The Ringg AI API follows RESTful principles, making it intuitive and easy to integrate with your applications. All API requests should be made to the base URL. The API accepts and returns data in JSON format. Ensure your requests include the appropriate Content-Type header for POST and PATCH requests. version: 2.0.0 servers: - url: https://prod-api.ringg.ai/ca/api/v0 security: [] tags: - name: workspace description: Endpoints for managing your workspace. - name: agent description: Endpoints for managing assistants (agents). - name: calling description: Endpoints for making and managing calls. - name: campaign description: Endpoints for managing campaigns. - name: analytics description: Endpoints for accessing call analytics and performance metrics. - name: termination description: Endpoints for terminating active calls using different methods. - name: knowledgebase description: Endpoints for managing knowledge bases. paths: /calling/call-details: get: tags: - calling summary: Get Call Details description: >- Retrieves detailed information about a specific call using its unique identifier. Use the send_analysis parameter to include analysis data in the response. operationId: getCallDetails parameters: - name: X-API-KEY in: header description: (Required) Your Ringg AI API key. required: true schema: type: string example: 7251cb4b-3373-43a4-844c-b27a1d45e0c9 - name: id in: query description: (Required) The unique identifier (UUID) of the call. required: true schema: type: string example: 550e8400-e29b-41d4-a716-446655440000 - name: send_analysis in: query description: >- (Optional) Whether to include analysis data (platform_analysis and client_analysis) in the response. required: false schema: type: boolean default: false example: true responses: '200': description: Call details retrieved successfully. content: application/json: schema: type: object properties: status: type: string example: success data: type: object properties: id: type: string description: The unique identifier of the call example: 550e8400-e29b-41d4-a716-446655440000 call_direction: type: string description: The direction of the call enum: - inbound - outbound - webcall example: outbound call_status: type: string description: The current status of the call enum: - registered - ongoing - retry - error - completed - failed - cancelled - forwarded example: completed call_sub_status: type: string description: >- The sub-status of the call providing more detail on the call outcome enum: - IN_DB - QUEUED - ACCEPTED - RATE_LIMITED - RETRY_LIMIT_REACHED - RETRY_SCHEDULED - FAILED - USER_DID_NOT_JOIN - USER_LEFT - USER_BECAME_IDLE - CAMPAIGN_TIME_EXCEEDED - MAX_CALL_DURATION - NOT_ABLE_TO_CALL - USER_TERMINATED - DND_SKIPPED - VOICEMAIL_DETECTED - VOICEMAIL_DETECTED_VIA_LLM - PRE_CALL_API_FAILED - RECONCILED_TO_ERROR_FROM_REGISTERED - RECONCILED_TO_ERROR_FROM_RETRY - RECONCILED_TO_ERROR_FROM_ONGOING - RECONCILED_TO_COMPLETED_FROM_ONGOING example: ACCEPTED from_number: type: string description: The phone number the call was made from example: '+1234567890' to_number: type: string description: The phone number the call was made to example: '+0987654321' callee_name: type: string description: The name of the person called example: John Doe agent_id: type: string description: The ID of the agent that handled the call example: agent-123-456 initiation_time: type: string format: date-time description: When the call was initiated example: '2024-01-15T14:30:00Z' recording_url: type: string description: >- URL to the call recording. Valid for 24 hours after the call; download the recording within that window to retain it. example: https://example.com/recordings/call-123.mp3 transcription_url: type: array description: Array of conversation turns between bot and user items: type: object properties: bot: type: string description: Bot's message user: type: string description: User's message example: - bot: Hello, how can I help you today? - user: I need information about my order - bot: >- I'd be happy to help you with that. Can you provide your order number? - user: Sure, it's ORDER-12345 platform_analysis: type: object description: >- Platform-generated analysis of the call (only included when send_analysis=true) example: sentiment: positive call_outcome: successful duration_score: 8.5 client_analysis: type: object description: >- Client-specific analysis of the call (only included when send_analysis=true) example: lead_score: 85 follow_up_required: true customer_satisfaction: high examples: basic_response: summary: Basic call details (send_analysis=false) value: status: success data: id: 550e8400-e29b-41d4-a716-446655440000 call_direction: outbound call_status: completed call_sub_status: ACCEPTED from_number: '+1234567890' to_number: '+0987654321' callee_name: John Doe agent_id: agent-123-456 initiation_time: '2024-01-15T14:30:00Z' recording_url: https://example.com/recordings/call-123.mp3 transcription_url: - bot: Hello, how can I help you today? - user: I need information about my order - bot: >- I'd be happy to help you with that. Can you provide your order number? - user: Sure, it's ORDER-12345 with_analysis: summary: Call details with analysis (send_analysis=true) value: status: success data: id: 550e8400-e29b-41d4-a716-446655440000 call_direction: outbound call_status: completed call_sub_status: ACCEPTED from_number: '+1234567890' to_number: '+0987654321' callee_name: John Doe agent_id: agent-123-456 initiation_time: '2024-01-15T14:30:00Z' recording_url: https://example.com/recordings/call-123.mp3 transcription_url: - bot: Hello, how can I help you today? - user: I need information about my order - bot: >- I'd be happy to help you with that. Can you provide your order number? - user: Sure, it's ORDER-12345 platform_analysis: sentiment: positive call_outcome: successful duration_score: 8.5 client_analysis: lead_score: 85 follow_up_required: true customer_satisfaction: high '404': description: Not Found - The call does not exist. content: application/json: schema: type: object properties: detail: type: string example: Call not found '500': description: Internal Server Error. content: application/json: schema: type: object properties: detail: type: string example: An unexpected error occurred. ````