AsyncAPI channel · Netlify
· Netlify Webhooks and Build Hooks
build_hooks/{build_hook_id}
Inbound Build Hook. The subscriber (CMS, CI system, cron, etc.) issues
an HTTP POST against the per-hook URL returned by
`POST /api/v1/sites/{site_id}/build_hooks` to trigger a new build for
the site. Optional query parameters override default behaviour;
optional request body (URL-encoded) is exposed inside the build as
the `INCOMING_HOOK_BODY` environment variable.
Provider:NetlifyAsyncAPI: v2.6.0Spec: Netlify Webhooks and Build HooksOperations: 1Messages: 1
Channel address
build_hooks/{build_hook_id}
Parameters
build_hook_id — Unique identifier of the build hook (the `id` returned on the `buildHook` object).
Operations
publish
triggerBuildHook
Trigger a build for the site
Messages
buildHookTrigger
Inbound POST to a Netlify Build Hook URL. The body is optional and
is URL-encoded; Netlify exposes it inside the build as the
`INCOMING_HOOK_BODY` environment variable.
Content-Type: application/x-www-form-urlencoded
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.