register a webhook for Buttondown subscriber and email events
domain: docs.buttondown.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
POST to https://api.buttondown.com/v1/webhooks with url and event_types (e.g. email.created, email.sent)
Optionally set a signing_key so Buttondown includes an X-Buttondown-Signature: sha256=... header on each delivery
Verify signatures server-side using HMAC-SHA256 over the raw JSON payload with your signing_key
List or retrieve registered webhooks via GET /v1/webhooks or /v1/webhooks/{id} to confirm configuration
Update the url, event_types, or signing_key later via PUT /v1/webhooks/{id} rather than deleting and recreating
Known gotchas
Without a signing_key, deliveries carry no signature header — treat unsigned endpoints as unverifiable
A single webhook can subscribe to multiple event_types at once, so avoid provisioning one webhook per event unnecessarily
Tag-modification and subscriber/email/automation events all share the same webhook mechanism — filter by event_types rather than assuming separate infrastructure per category
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?