API webhooks
Component-composed endpoint inventory, configuration, signing secrets, deliveries, failures, retries, and pressure states.
Webhook endpoints and delivery lifecycle
Endpoint inventory, creation, details, signing secrets, successful and failed attempts, retries, disabled state, and pressure cases.
Complete screen
Production events
Separate endpoint configuration from application-owned delivery history.
- Endpoint
- Production events
- https://api.example.test/hooks/nitro
- Subscribed events
- 4 events
- deployment.created · incident.updated · member.invited · invoice.paid
- Delivery policy
- Enabled
- 10 second timeout · exponential retry managed by the application
Delivery attempts
Payload storage, redaction, response bodies, timeout policy, and retries remain application-owned.
| Attempt | Time | Response | Duration |
|---|---|---|---|
| 1 | 10:41:22 UTC | HTTP 202 Accepted | 184 ms |
Viewport
Ruby
test/dummy/app/components/gallery/compositions/api_webhooks_page.rbworkspace_surface do
render_header
case state
when "list" then render_list(webhook_rows.first(3))
when "empty" then render_empty
when "detail" then render_detail
when "create", "validation", "loading" then render_form
when "delivery-succeeded" then render_delivery(:success)
when "delivery-failed" then render_delivery(:failed)
when "retrying" then render_delivery(:retrying)
when "disabled" then render_disabled
when "signing-secret" then render_signing_secret
when "dense" then render_list(webhook_rows)
when "long" then render_long
when "mobile" then render_mobile
end
end