Event types

The events Daybook sends, and the data each one carries.

Every event arrives in the same envelope. Subscribe an endpoint to exact types, or * for all.

Event	Sent when
`webhook.test`	You choose Send test event on an endpoint's page in Developers → Webhooks, or call Send a test event.

webhook.test

data.endpoint_idstring
The endpoint the event was sent to, prefixed whe_.
data.messagestring
A fixed message saying this is a test event.

json

{
  "id": "evt_01JBXK8N3QZ7V2C4D5E6F7G8HJ",
  "type": "webhook.test",
  "created_at": "2026-10-29T14:31:40Z",
  "mode": "test",
  "data": {
    "endpoint_id": "whe_01JBXK4R7T2M9P5W3Y6A8C0D1E",
    "message": "This is a test event from Daybook."
  }
}

Payer call events

The Payer calls workflow sends these events as a call moves. Each arrives in the same envelope, with the call object in data and your metadata echoed.

Event	Sent when
`call.started`	Daybook dialed and is working the phone tree.
`call.on_hold`	Daybook reached the hold queue. Carries `hold_seconds` so far.
`call.handoff_ready`	A rep answered a `handoff` call. Carries the bridge details and the questions to ask.
`call.completed`	The call ended with a structured answer: status, reference number, rep name, next step and the call type's details.
`call.failed`	The call could not be completed. `data.ended_reason` says why.
`call.canceled`	The call was stopped by Cancel a call or by a person in the Daybook app, before it dialed or while it ran.