/events
Long-poll endpoint for retrieving new events from a previously registered queue. The client issues a GET request with queue_id and last_event_id; the server holds the connection open until new events arrive (or dont_block=true is supplied). The response body contains an events array of typed event objects whose schemas are documented below.
Channel address
Parameters
queue_id— Identifier of an event queue previously returned by POST /api/v1/register.last_event_id— The highest event ID the client has already received and is acknowledging. The server will return only events with a higher ID.dont_block— If true, the server returns immediately with whatever events are currently queued (possibly an empty array). Defaults to false, which causes the server to long-poll for new events.
Operations
Messages
application/jsonAbout 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.