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.
baseId — The ID of the base the webhook is registered on.
webhookId — The ID of the webhook.
Operations
subscribe
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.
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.