webhook
Smart routing event
The Smart routing webhook event is a little more tricky because the webhook requires a response from you within two seconds. When the webhook lands on your <em>endpoint</em>, your endpoint must communicate the response object below. We advise you to consult the description of each attribute, which are all mandatory. This event can apply to an IVR.
To certify that the request was sent by Ringover, the x-ringover-webhook-signature header must be a JWT signed with the webhook key you can find in the IVR redirection step scenario configuration, using algorithm HS512.
postWebhooksmart_routing
Payload
Example payload
{
"event": "routing",
"resource": "call",
"timestamp": 1554823493.762305,
"data": {
"call_id": 1234567890987654400,
"direction": "inbound",
"from_number": "33601020304",
"to_number": "33101020304"
}
}Response
Successful operation
Example response
{
"name": "redirections",
"dispatch": "ringall",
"max_attempts": 1,
"is_stay_not_connected": true,
"is_stay_planned_snoozed": true,
"ring_overlap": 15,
"groups": [
{
"ring_duration": 30,
"is_caller_id": true,
"is_head_line": true,
"order": 1,
"id": 1234567
}
],
"agents": [
{
"agent_type": "agent_external",
"ring_duration": 25,
"order": 1,
"number": 33123456789,
"is_caller_id": true
}
]
}