AsyncAPI channel · Stedi · Stedi Event Destinations (webhooks)

`{destinationUrl}`

A single HTTPS POST carrying one thin event envelope. Stedi treats ONLY 2xx as success; 3xx, 4xx, 5xx and network failures all trigger a retry.

Open source AsyncAPI → All Stedi channels Stedi provider profile

Provider: Stedi AsyncAPI: v3.0.0 Spec: Stedi Event Destinations (webhooks) Operations: 1 Messages: 7

Channel address

{destinationUrl}

Operations

receive

receiveEvent

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.

Browse every event-driven channel on the APIs.io network or compare with the broader Agent Skill and MCP server surfaces of the same providers.