Webhooks

Get delivery events pushed to your server instead of polling the log — bounces, opens, and unsubscribes arrive as HTTP POSTs to a URL you control.

Webhook endpoints require a key with the webhooks scope and a plan that includes webhooks.

How webhooks work

Register a URL and the events you care about. When an event fires, InBuzzed delivers a JSON payload to your URL. Your endpoint should respond 2xx quickly and process the payload asynchronously.

Manage webhooks

GET/webhooks

POST/webhooks

PATCH/webhooks/:id

DELETE/webhooks/:id

curl

curl -X POST https://api.inbuzzed.com/api/v1/esp/webhooks \
  -H "X-Api-Key: ib_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://yourapp.com/hooks/inbuzzed"
  }'

Handling deliveries

Respond fast. Return 200 before doing heavy work — queue the payload and process it out of band.
Expect retries. Deliveries can arrive more than once; make your handler idempotent (dedupe on the event ID).
Use HTTPS. Webhook URLs should always be TLS endpoints you control.