Post call webhook
After each analyzed call, OSVI sends the post-call analysis results to every webhook integration configured on the agent (Agent → Post-Call Analysis → Integrations). The HTTP method, custom headers, and request body are all configurable per integration. The schema below describes the default Auto body mode with every data section enabled — each section can be toggled off individually, or replaced entirely with a Custom Template body. A section that is enabled but has no data for the call is omitted from the payload.
call_status: picked), and only when Post-Call Analysis is enabled on the agent.Configuring a webhook
Each integration lets you configure:Request body modes
Auto mode
In Auto mode you choose which data sections to include. Each enabled section contributes its fields to a flat JSON body; sections with no data for a given call are omitted.Custom Template mode
In Custom Template mode you write the JSON body yourself, using{{expression}} placeholders that are resolved against the call’s data at delivery time:
"{{structured_output}}"), the raw type is preserved — objects stay objects, numbers stay numbers. When an expression is embedded in a longer string, it is interpolated as text. Expressions that don’t resolve become null.
Linking retries and callbacks to the original call
Every follow-up call Osvi places gets its owncall_log_id. That includes automatic retries of unanswered calls and callbacks the caller asked for (“call me in 10 minutes”). Each of these calls carries parent_call_log_id, which always points to the first call, the one you triggered (its call_log_id is the call_id returned when you placed it). It never points to the previous attempt, so you can group a whole chain under one key. On the original call, parent_call_log_id equals its own call_log_id.
Delivery, logging, and retries
- Your endpoint should respond with any 2xx status within 15 seconds to acknowledge receipt.
- Every delivery attempt — including the request payload, response status, and response body — is recorded in Integration Logs on the agent’s Post-Call Analysis tab.
- Failed deliveries (non-2xx responses, timeouts, connection errors) are not retried automatically, but can be retried manually from the Integration Logs view, individually or in bulk.
- Use the Test button on an integration to send a sample payload and verify your endpoint before going live.
Verifying requests
Turn on webhook signing in Settings → Webhook signing to have Osvi sign every webhook with your account’s secret. Your server can then check theX-Signature header and drop anything that didn’t come from Osvi. See Verifying webhook signatures.Body
The call_log_id of the first call in this call's chain of automatic retries and callbacks: the call you triggered. Every follow-up call reports the original call here, never the previous attempt, so all calls in a chain share one value. On the original call it equals its own call_log_id. Part of the Call Info section.
"3f1c9a2e-7b4d-4e8a-9c6f-2d5b8e1a0f47"
Data from the source that triggered the call. For API-triggered calls this carries the custom fields from the original request body; for campaign (CSV) calls it carries the row's metadata columns. Always includes phone_number and person_name when available. Sent when the Call Trigger Data section is enabled.
Response
Webhook received successfully. Return any 2xx status to acknowledge receipt. Non-2xx responses are recorded as failed deliveries in the agent's Integration Logs and can be retried from the dashboard.
