AsyncAPI channel · Airtable · Airtable Webhooks API

/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.

Provider: Airtable AsyncAPI: v2.6.0 Spec: Airtable Webhooks API Operations: 1 Messages: 1

Channel address

/v0/bases/{baseId}/webhooks/{webhookId}/payloads

Parameters

Operations

listWebhookPayloads
List queued webhook payloads

Messages

WebhookPayloadList
Envelope returned when listing queued webhook payloads.
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 Naftiko capability, Agent Skill, and MCP server surfaces of the same providers.