Triggered at the end of a call to provide detailed Call and End User information.
The on_call_end
webhook is triggered at the conclusion of a call in the Altur platform. This webhook provides detailed information about the call, the assistant involved, and the end user. Use this webhook to keep your backend or CRM updated with the latest call data.
POST
application/json
X-Altur-Signature
header for HMAC verification.Here’s an example of the payload sent with the on_call_end
event:
Field | Type | Description |
---|---|---|
event_type | string | Event type (on_call_end ). |
id | string | Unique identifier for the call. |
type | string | Call type (outbound or inbound ). |
status | string | Status of the call enum value (e.g., ended ). |
phone_number_from | string | E.164 formatted number. |
phone_number_to | string | E.164 formatted number. |
answered_by | string | Indicates who answered the call (human , machine or unknown ). |
created_at | datetime | ISO formatted date time of when the call was created. |
started_at | datetime | ISO formatted date time of when the call started. |
ended_at | datetime | ISO formatted date time of when the call ended. |
duration | int | Call duration in seconds. |
billed_duration | int | Billed call duration in seconds. |
recording_url | string | URL to download the call recording. |
transcript | array | Call transcript object. |
Field | Type | Description |
---|---|---|
id | uuid | Unique identifier for the assistant. |
nickname | string | Assistant’s nickname. |
name | string | Assistant’s name. |
Field | Type | Description |
---|---|---|
id | uuid | Unique identifier for the end user. |
status | string | Current status of the user enum value (e.g., converted ). |
display_name | string | Display name of the user. |
phone_number | string | User’s phone number (E.164 format). |
context | string | Additional user-specific information. |
extracted_data | object | Key-value pairs of extracted data. |
tags | array | Array of tag names corresponding to tags assigned to the last campaign user or current thread. |
Your endpoint should return a 200 OK status code to confirm receipt of the webhook. For information on retry behavior in case of failures, see the Retry Policy section in the Webhook Overview.
Each request includes an HMAC signature in the X-Altur-Signature
header. Refer to the Securing Your Webhooks section for instructions on validating webhook requests.
CRM Integration
Use the on_call_end
webhook to update call logs and user interaction data in your CRM system.
Analytics
Process transcripts and user status to generate insights or trigger follow-up actions.
Data Enrichment
Automatically store extracted data, like account numbers or due dates, in your system for further use.