/v0/bases/{baseId}/webhooks/{webhookId}/payloads
Polled by the receiver after a ping to retrieve queued change payloads for the webhook. Payloads are returned in transaction order and paginated via the `cursor` query parameter. The response includes a new `cursor` indicating the next transaction number to request and a `mightHaveMore` flag indicating whether additional payloads remain.
Channel address
Parameters
baseId— The ID of the base the webhook is registered on.webhookId— The ID of the webhook.
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.