AsyncAPI channel · Leap
· Leap Webhook Events
/
Partner receiver URL registered through the general webhook platform. The event types the receiver gets are selected at subscription time.
Channel address
/
Operations
receive
receivePlatformEvent
Receive a Leap webhook platform event
Messages
connect_session.updated
A customer Leap Connect session was created, advanced, closed or completed.
Content-Type:
connect_session.authorization_updated
A utility data-sharing authorization (Leap Connect redirect or CAISO direct-to-utility) changed state.
Content-Type:
meter.created
A new meter was created in the partner account, partner-created or customer-authorized.
Content-Type:
meter.enrollment.global-status.updated
Global enrollment status updated
Content-Type:
meter.enrollment.required-actions.updated
New, updated or resolved partner actions on a meter. When every action is resolved a final event carries an empty required_actions object.
Content-Type:
meter.enrollment.participation-status.updated
Participation preference updated
Content-Type:
meter.enrollment.group.updated
The start date, end date or meter membership of a VPP market group changed.
Content-Type:
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.