Webhooks API
How an app is told what happened in an organization: its subscriptions and their deliveries.
How an app learns what happened in a organization. An app subscribes to topics from a public, versioned catalogue (WebhookTopic); the service reads the core journals, turns each fact into the event it stands for and delivers it to every subscription of an installation granted the topic's scope — signed per installation, retried with backoff for about a day, logged, and redeliverable.
- Base URL
https://webhooks.getmanifold.io- Auth
- A bearer token on every call. See the quickstart.
- OpenAPI
- webhooks.openapi.json
subscriptions
Where an app is told what happened in a organization.
- GET
/subscriptionsThe calling app's webhook subscriptions in this organization: each with its URL and topics - PUT
/subscriptions/{subscriptionId}Subscribe the calling app to topics at a URL - DELETE
/subscriptions/{subscriptionId}Let a subscription go - GET
/signing-secretThe secret the calling app's deliveries are signed with in this organization
deliveries
The delivery log: what was sent to the calling app, and how it answered.
- GET
/deliveriesThe calling app's delivery log - GET
/deliveries/{deliveryId}One of the calling app's deliveries, with its attempts and the app's last answer - POST
/deliveries/{deliveryId}/redeliverSend one of the calling app's deliveries again
events
The webhooks append-only event log.