webhook

Summary available event

Sent on a call.aftercall subscription when a Ringover call summary is ready (event: summary_available).

summary is the summary text. ringover_call_path opens the call in the Ringover app.

For Empower users, the summary, the transcription, and the follow-up actions are sent together through the empower event.

To certify that the request was sent by Ringover, verify the request signature with your webhook key — see Securing your webhooks under the webhook tag (V1: JWT HS512 in X-Ringover-Webhook-Signature, with the deprecated Authorization header for backward compatibility; V3, on request: Base64 HMAC-SHA256 in X-Ringover-Webhook-Signature-V3).

postWebhooksummary_available

Payload

eventstring
resourcestring
timestampnumber
attemptinteger

Example payload

{
  "event": "summary_available",
  "resource": "aftercall",
  "timestamp": 1554823493.762305,
  "data": {
    "call_id": "1234567890987654400",
    "channel_id": "1234567890987654422",
    "summary": "The customer confirmed the delivery date and asked for a written quote.",
    "ringover_call_path": "https://app.ringover.com/call-logs/1234567890987654400"
  }
}

Response

Successful operation

Changes

Webhooks have no change history: a webhook is keyed by its event name rather than a path and method, so no recorded change can name it.