AsyncAPI channel · Leap · Leap Webhook Events

partner receiver_url

Emitted as a customer moves through a Leap Connect or direct-to-utility authorization session.

Provider: Leap AsyncAPI: v3.0.0 Spec: Leap Webhook Events Operations: 1 Messages: 2

Channel address

partner receiver_url

Operations

receive
receiveConnectSessionEvents

Messages

connect_session.updated
Connect session updated
Content-Type: application/json
connect_session.authorization_updated
Connect session authorization updated
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/partner-receiver-url"
All event channels
curl "https://apis.io/api/v1/channels?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

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