Skip to main content
GET
Get Call Details
Read only
Recommended. This endpoint is part of the public /v1 API reference and is the supported path for new integrations. See the migration guide for versioning guidance.
Fetches the complete record for a single call by call_id. The response includes the call’s current status, the destination and source numbers, the assigned agent_id, timestamps for when the call was placed and when it ended, and, once the call reaches a terminal state, the duration, recording URL, and transcript. Use this endpoint to poll for completion after triggering a call, render a call detail page, or sync per-call data into a downstream system.

When to use this

  • Synchronous workflows: trigger a call and poll until it reaches a terminal status before continuing.
  • Operational dashboards: render a call detail view with status, duration, and the linked agent.
  • CRM sync: write back the call outcome to the customer record the call was made for.

Polling vs. webhooks

For production traffic, webhooks are the preferred way to know when a call has ended, they avoid the request volume and latency of repeated polling. Subscribe to call.completed and call.failed via Create Webhook and use this endpoint only when you specifically need to fetch the latest state on demand (for example, a user opens a call detail page). When polling is required, the call’s status transitions from initiated to in-progress, then to one of completed, failed, busy, or no-answer. Poll every 5 to 10 seconds with an exponential cap; do not poll faster than once per second.

Path parameters

Errors

  • 400 Bad Request is returned when the call ID format is invalid.
  • 401 Unauthorized is returned when the API key is missing or invalid.
  • 403 Forbidden is returned when the call does not belong to your organization.
  • 404 Not Found is returned when the call does not exist.
  • 500 Internal Server Error is returned on an unexpected server-side failure.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

id
string
required

Call ID

Example:

"call_abc123"

Response

Call returned successfully.

id
string
required

Signed call ID

Example:

"call_abc123"