/v1/webhooks

A webhook tells Apptoto to POST a JSON payload to a URL each time something happens on your account -- a participant confirms, a booking request is completed, a message comes in. Each webhook watches one event_type and sends to one url. To send the same event to two URLs, create two webhooks.

Returns every webhook on the account. Pass id to fetch a single webhook instead.

Webhooks that email or text someone instead of calling a URL are managed in Settings > Integrations > Webhooks and are not returned here.

Example Result:

{
  webhooks: [ {
    id: 4512,
    event_type: "participant_confirmed",
    url: "https://example.com/apptoto/confirmed",
    enabled: true,
    created_at: "2026-10-12T15:04:11.000-07:00",
    updated_at: "2026-10-12T15:04:11.000-07:00"
  }]
}

With id, the result is a single object:

{
  webhook: {
    id: 4512,
    event_type: "participant_confirmed",
    url: "https://example.com/apptoto/confirmed",
    enabled: true,
    created_at: "2026-10-12T15:04:11.000-07:00",
    updated_at: "2026-10-12T15:04:11.000-07:00"
  }
}

An id that does not belong to the account returns 404.

See Webhook Payloads for what Apptoto sends to the URL.

OAuth scope

Calls authenticated with an OAuth 2.0 bearer token must include the webhooks:read scope. A token without it receives a 403 insufficient_scope response. HTTP Basic auth is not scope-gated.