Announcing Headless Webhooks API Programmatically... ▪️ list webhook events ▪️ retrieve events ▪️ list event attempts ▪️ manually replay events ▪️ rotate signing secrets Everything in the dashboard is now available in the API.

What you can build with it: ▪️ automated recovery ▪️ delivery alerts ▪️ secret rotation ▪️ agent-driven debugging Everything in the dashboard is now available in the API, SDKs, CLI, and MCP server.

1️⃣ List events List the events delivered to a webhook. Each one carries the delivery status for that endpoint: success, failed, attempting, or pending.

2️⃣ Retrieve event See what your endpoint returned. Retrieve Event gives you the payload we sent and when the next automatic retry is scheduled.

3️⃣ Reply events Once your endpoint is healthy again, replay the event. This is the same action as the Replay button in the dashboard.

4️⃣ Rotate signing secrets If a signing secret leaks, or you rotate secrets as routine hygiene, you no longer need the dashboard to do it. The response includes the new secret, so there's no second request.

These endpoints are part of a larger move to bring the full functionality of the dashboard into the API, CLI, and MCP server. Read the full changelog 👇

Manual replay and rotating signing secrets in the API is the stuff I end up needing at 11pm, not in the dashboard demo. Dashboard parity for webhook attempts is overdue in a good way.

Being able to inspect attempts and replay them over API is huge. That turns webhook recovery into an operable workflow instead of a dashboard scavenger hunt.

Replay is the one people will misuse. It is only safe if the receiver is idempotent, and most teams find that out the week a provider fires the same event three times.