AsyncAPI channel · Netlify · Netlify Webhooks and Build Hooks

`build_hooks/{build_hook_id}`

Name: build_hooks/{build_hook_id}
Creator: Netlify

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.

Open source AsyncAPI → All Netlify channels Netlify provider profile

Provider: Netlify AsyncAPI: v2.6.0 Spec: Netlify Webhooks and Build Hooks Operations: 1 Messages: 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.

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.