Ringostat
Log in

Webhooks: call results

~5 min · When reports are sent, the payload, Basic/OAuth 2.0 authorization and delivery.

After each finished call Ringostat sends the call report to your URL. Set it in the campaign → “Webhook and reports” block (or webhookURL in voiceagent_create_campaign).

“When to send webhook”: all — every call (default); answered — answered calls only; interaction — calls where the person pressed a key or, in AI-agent campaigns, spoke. A number that used up all its attempts is reported only with all.

By default it is a POST with Content-Type: application/json and a JSON-RPC 2.0 body: method is always callCompleted, the call data is in params.

POST https://your-app.example/webhooks/ringostat
Content-Type: application/json

{ "jsonrpc":"2.0", "method":"callCompleted", "id":1760437456000000000,
  "params":{ "campaign_id":799, "campaign_name":"Order confirmation",
    "number_id":1001, "phone_number":"+14155550123", "status":"completed",
    "start_time":1760437400, "answered_time":1760437408, "end_time":1760437456,
    "duration":56, "connected_duration":48, "wait_time":8,
    "custom_fields":{"name":"John"}, "dtmf_responses":[],
    "voicemail_detected":false, "transferred_to":"",
    "aisdr_final_response":{ … } } }

status: completed, answered, transferred, voicemail, abandoned, failed or retry. Times are Unix seconds, durations are in seconds. aisdr_final_response is the structured report of an AI-agent (aisdr) call; its keys come from the campaign's report settings. A number that used up its attempts arrives with status failed plus attempt_count and max_attempts. The recording is not in the payload: voiceagent_get_call_detail returns it.

For campaigns with an AI agent the payload also has tools: the last successful result of each tool the agent called in the conversation, under the tool's name. This is how, for example, a Servio HMS booking number or the number of a created order reaches the webhook. Failed calls and refusals are not included; a tool that was not called has no key.

"tools": {
  "servio_create_booking": { "ok": true, "booking_id": "100245",
    "payment_link": "https://pay.example.com/booking?account=100245", … } }

In your own body template, refer to them as {{tools.<tool>.<field>}}. Add ? at the end when the tool may not have been called: the field is then null, while without ? the webhook for such a call is not sent. A test request from the cabinet has no tool results: a field with ? is null there, and a field without ? shows a <sample: tools…> placeholder.

{"phone":"{{phone_number}}","booking":"{{tools.servio_create_booking.booking_id?}}",
 "payment":"{{tools.servio_create_booking.payment_link?}}"}

Any integration tool works the same way. For example, a Nova Poshta waybill created during the call: nova_poshta_create_waybill returns ttn, delivery_cost, estimated_delivery_date, warehouse and city.

{"phone":"{{phone_number}}","ttn":"{{tools.nova_poshta_create_waybill.ttn?}}",
 "delivery_date":"{{tools.nova_poshta_create_waybill.estimated_delivery_date?}}"}
Requests are not signed. To authenticate them, choose HTTP Basic or OAuth 2.0 under “Authorization” in the “Webhook and reports” block (project admins). There you can also switch the method to PUT or PATCH and replace the body with your own JSON or form template. A webhook with authorization needs an https URL and follows no redirects.
Reply with 2xx within 30 seconds (20 seconds with Basic or OAuth 2.0). A failed delivery is not retried, except one replay after an OAuth 401. Every attempt is shown in the call card → “Webhook delivery”; send a report again with “Resend webhook” or voiceagent_resend_call_webhook. Drop duplicates by number_id + end_time.