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.

Work with this as data

Every channel here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for event channels

4 MCP tools reach this
  • find_channelsBrowse and filter every channel in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This channel 
curl "https://apis.io/api/v1/channels/destinationurl"
All event channels 
curl "https://apis.io/api/v1/channels?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.