Stedi POSTs the event envelope to the destination URL. The consumer verifies the webhook-signature header, deduplicates on webhook-id, and then fetches current resource state from the REST API using r
Messages
enrollment.activated
A transaction enrollment request reached LIVE status.
Content-Type: application/json
enrollment.rejected
A payer rejected a transaction enrollment request.
Content-Type: application/json
enrollment.updated
An enrollment changed — status, payer, contacts or tasks.
Content-Type: application/json
enrollment.task.assigned
A new provider-action task was created on an enrollment.
Content-Type: application/json
enrollment.task.completed
The provider completed an assigned enrollment task.
Content-Type: application/json
enrollment.task.deleted
An enrollment task was superseded or removed.
Content-Type: application/json
event.ping
A validation test event used to confirm a destination is reachable.
Content-Type: application/json
About AsyncAPI
The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.