Learn how to set up Webhooks and receive Server Events with OutRival.
x-signature
header contains a signature generated from the payload using the Webhook Secret. This signature must be used to verify that the request is indeed from OutRival.
The payload of the webhook is structured as follows:
status-changed
, conversation-updated
, function-call
VOICE
, TEXT
, SMS
queued
, ringing
, in-progress
, forwarding
, ended
x-signature
header in each incoming request. This signature is generated by hashing the payload with the Webhook Secret. Your endpoint should compute the hash with the received payload and the secret you provided when setting up the webhook. If the computed hash matches the x-signature
header, the request can be considered authentic and from OutRival.
Here are a few examples of how to verify the signature in different programming languages:
x-signature
to confirm the authenticity of the incoming requests.