Source type

Buildkite Source Configuration

Buildkite sources receive pipeline, build, job, agent, and annotation webhooks with timestamped Buildkite signatures.

BUILDKITEPOST, PUT, PATCH, DELETEWebhook TokenDeveloper tools
Buildkite sends webhook traffic to a FastHook source, FastHook validates the provider contract, records the request, and routes accepted events through connections to destinations.BuildkiteProviderPOST, PUT, PATCH, DELETESignedFastHookSource URLBUILDKITEProvider credentialsignatureVerify before queue401 on auth failure405 on wrong methodAcceptedRequestverified: trueConnections route the accepted request to destinationsFilters, transformations, retries, replay, and destination signatures stay downstream from source verification.

Buildkite configuration

Create a Buildkite source, keep POST and PUT and PATCH and DELETE enabled, and provide the configured Webhook Token values for provider signature. FastHook uses these settings to validate each Buildkite delivery before it enters the routing workflow.

Source Type

BUILDKITE

Allowed methods

POST, PUT, PATCH, DELETE

Authentication

Provider signature

Credential fields

Webhook Token

Buildkite source config
{
  "type": "BUILDKITE",
  "config": {
    "auth_type": "PROVIDER_SIGNATURE",
    "auth": {
      "provider": "BUILDKITE",
      "webhook_signing_secret": "provider-secret"
    },
    "allowed_http_methods": ["POST","PUT","PATCH","DELETE"]
  }
}

Buildkite request contract

FastHook verifies x-buildkite-signature by signing timestamp + '.' + raw body with HMAC-SHA256.

POSTPUTPATCHDELETE

Buildkite headers

Preserve x-buildkite-signature when sending Buildkite test deliveries. FastHook evaluates this request context before accepting the payload, so missing or modified values remain visible as rejected requests instead of routed events.

x-buildkite-signature

Contains timestamp and signature parameters.

Buildkite setup

  1. Create a Buildkite pipeline webhook using the FastHook Source URL.
  2. Paste the webhook token into FastHook.
  3. Route by event type or pipeline slug for CI automation.

Continue with Buildkite