End of Call

Sends an HTTP notification to your endpoint when a call ends, regardless of attempt. The payload contains the full transcript, recording, duration, and analysis of the completed call.

Delivery

• Method: POST
• Content-Type: application/json
• Request timeout: 30 seconds. If your endpoint does not respond in 30s, the attempt is treated as failed and retried.
• Authorization: If a bearer token is configured for the agent, requests include an Authorization: Bearer <token> header.

Payload

idstring

Unique call ID, consistent across all webhooks for the same call.

session.idstring

Session ID that groups all call attempts to the same customer.

startedAtstring

Call start date-time in ISO 8601.

endedReasonstring

Why the call ended (for example customer-ended-call, user-not-contacted).

messagesarray

Full conversation transcript.

customer.namestring

Optional. Present when a name was provided when creating the call.

customer.phoneNumberstring

Destination phone number in E.164 format.

variableValuesobject

Input variables provided when the call was created.

durationSecondsinteger

Total call duration in seconds.

detailsURLstring

URL to view call details in the dashboard.

recordingURLstring

Optional. URL to download the audio recording. Present only when a recording is available.

analysis.successEvaluationboolean

Whether the success criteria was met.

analysis.structuredDataobject

Output variables and extracted values.

analysis.summarystring

Natural-language summary of the call.

Message details

The messages field contains the complete call transcript:

• role: Participant role (system, agent, user)
• message: Message content

Responding to events

Return any HTTP 2xx status code to acknowledge receipt. Response body is ignored.

Any of the following is treated as failure and triggers a retry:

• 3xx, 4xx, or 5xx response
• Network error (connection refused, DNS failure, TLS error)
• No response within the 30-second timeout

Your endpoint must be idempotent. Since non-2xx responses are retried, the same event may be delivered multiple times. Deduplicate using id.

Respond well under 30 seconds—ideally acknowledge immediately (for example by queueing the event) and do heavy processing asynchronously.

Retry policy

Failed deliveries are retried automatically with exponential backoff (each delay is 3× the previous one):

Attempt	Delay after previous attempt
1	— (initial delivery)
2	5 seconds
3	15 seconds
4	45 seconds
5	2 min 15 sec
6	6 min 45 sec
7	20 min 15 sec
8	1 hr 45 sec
9	3 hr 2 min 15 sec

After nine attempts the event is dropped and won't be resent. If your endpoint was down longer than the retry window, reconcile state using the API instead of waiting for redelivery.

Payload

1{
2  "id": "cHYqKdGz25Rq",
3  "session": {
4    "id": "sn_8Qd1mTbR"
5  },
6  "startedAt": "2024-09-24T18:20:22.724Z",
7  "endedReason": "customer-ended-call",
8  "messages": [
9    {
10      "role": "system",
11      "message": "You are a helpful assistant"
12    },
13    {
14      "role": "agent",
15      "message": "Hello"
16    },
17    {
18      "role": "user",
19      "message": "Hi"
20    }
21  ],
22  "customer": {
23    "name": "Jane Doe",
24    "phoneNumber": "+15551234567"
25  },
26  "variableValues": {
27    "myVariable": "myValue"
28  },
29  "durationSeconds": 15,
30  "detailsURL": "https://fonema.ai/shareable/cHYqKdGz25Rq",
31  "recordingURL": "https://fonema.ai/api/v1/storage/calls/cHYqKdGz25Rq.mp3",
32  "analysis": {
33    "successEvaluation": true,
34    "structuredData": {
35      "myData": "myValueFromCall"
36    },
37    "summary": "The customer confirmed the appointment."
38  }
39}