Skip to main content

Call Status

Track the real-time progress of your voice conversations using the HuskyVoice API or by monitoring state changes.


curl -s https://api.huskyvoice.ai/v1/calls/call_abc123 \
-H "x-api-key: YOUR_API_KEY"

Sample Response:

{
"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 for the call.
statusCurrent lifecycle state — see Call States below.
agent_idThe AI agent assigned to this call.
contact_numberThe destination phone number in E.164 format.
contact_nameName of the contact, if provided at creation.
contact_emailEmail of the contact, if provided at creation.
additional_infoCustom key-value pairs passed in at creation.
scheduled_atWhen the call was scheduled to start.
completed_atWhen the call finished, or null if not yet completed.
errorError details if the call failed, otherwise null.
created_at / updated_atRecord creation and last-update timestamps.

Call States

Every HuskyVoice conversation moves through a defined lifecycle. You can use these states to trigger custom business logic in your application.

StateDescription
initiatedThe request has been received and is waiting for the telephony bridge.
ringingThe destination phone is currently ringing.
in_progressThe AI agent and the user are actively talking.
completedThe conversation has finished successfully.
failedThe call could not be completed (e.g., busy signal, invalid number).
cancelledThe call was stopped by your system before it was answered.

Monitoring Tip

For high-volume integrations, we recommend using Outbound Webhooks to receive state changes automatically instead of polling the API. See the Common Use Cases guide for details on how to set these up.