webhook

Empower event

Sent on a call.aftercall subscription for Empower users when after-call data is ready (event: empower).

The payload carries summary, transcription, follow_up_actions, and empower_call_path together.

For Ringover users, the summary is sent through the summary_available 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).

postWebhookempower

Payload

eventstring
resourcestring
timestampnumber
attemptinteger

Example payload

{
  "event": "empower",
  "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.",
    "transcription": "Agent: Hello, how can I help you today?",
    "follow_up_actions": "Send the quote and schedule a follow-up call."
  }
}

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.