Outgoing webhooks

Outgoing webhooks are events that Bunce sends to a URL you control when something happens in your account. Instead of polling the API for changes, your server receives a POST request as soon as an event occurs.

Use them to sync delivery results with your own systems, trigger follow-up workflows, or keep an audit trail of every message Bunce sends on your behalf.

Setup

Enable webhooks from the Bunce dashboard: go to Settings > API & Webhook and set your Webhook URL. All events are delivered to that single URL. If no URL is configured, no webhooks are sent.

Delivery

• Method: POST
• Content type: application/json (the payload object is the request body)
• Header: X-Sender: Bunce
• Retries: up to 4 attempts, backoff 5s, 15s, 35s. Respond 2xx to acknowledge; anything else (or a timeout) is treated as a failure and retried.

Because a failed delivery is retried, your endpoint can receive the same event more than once. Use the event_id to discard duplicates.

Payload conventions

Every event payload includes:

• event: the event name, prefixed with its family (e.g. broadcast.sent, broadcast.delivered, broadcast.failed).
• event_id: a unique id for the event.

Event families

Event families are grouped by the area of Bunce they come from. Today Bunce sends broadcast events; more families may be added over time, and each will document its own set of events and payloads here.

• Broadcast events (currently available)