Call Status

Read the live state and details of a call with GET /v1/calls/{call_id}, and the states a call moves through.

Showing instructions for Xebit VoiceCloud.Showing instructions for Xebit VoiceKit, on your own infrastructure. Switch with the selector at the top. Updated 22 October 2026.

Read where a call is and what has happened on it with GET /v1/calls/{call_id}. For high volumes, let outbound webhooks tell you instead of polling.

Get a call

GET/v1/calls/{call_id}

Requires the calls:read scope.

curl -s "https://api.voice.xebit.ai/v1/calls/call_abc123" \
  -H "x-api-key: $XEBIT_API_KEY"
curl -s "https://<your-xebit-voicekit-host>/v1/calls/call_abc123" \
  -H "x-api-key: $XEBIT_API_KEY"

Sample response:

JSON
{
  "data": {
    "call_id": "550e8400-e29b-41d4-a716-446655440000",
    "status": "in_progress",
    "agent_id": "agent_123",
    "contact_number": "+919876543210",
    "contact_name": "Raj Patel",
    "contact_email": "raj@company.com",
    "additional_info": {
      "company": "Acme Corp"
    },
    "scheduled_at": "2024-01-27T03:02:00.000Z",
    "completed_at": null,
    "error": null,
    "created_at": "2024-01-27T03:00:00.000Z",
    "updated_at": "2024-01-27T03:00:00.000Z"
  }
}

Response fields

FieldDescription
call_idUnique identifier of the call.
statusWhere the call is in its lifecycle. See the states below.
agent_idThe agent assigned to the call.
contact_numberDestination number in E.164 format.
contact_nameContact name, if one was given when the call was created.
contact_emailContact email, if one was given when the call was created.
additional_infoThe custom key-value pairs sent at creation.
scheduled_atWhen the call was scheduled to start.
completed_atWhen the call ended, or null if it has not.
errorError details when the call failed, otherwise null.
created_at / updated_atWhen the record was created and last changed.

Call states

Every call moves through a fixed set of states. Use them to drive your own business logic.

StateMeaning
initiatedThe request has been accepted and is waiting to be handed to your carrier trunk.
ringingThe destination phone is ringing.
in_progressThe agent and the person are talking.
completedThe conversation finished normally.
failedThe call could not be completed, for example a busy line or an invalid number.
cancelledYour system stopped the call before it was answered.

On Xebit VoiceCloud, every request to this endpoint counts toward your rate limit, so prefer webhooks to tight polling loops.

On Xebit VoiceKit, polling load lands on your own infrastructure and counts toward the rate limits your deployment is configured with, so prefer webhooks to tight polling loops.

For high volume integrations, subscribe to outbound webhooks to receive state changes as they happen. Use Cases shows typical set-ups.