---
title: "Buildkite's webhooks (the URL a connection shows)"
description: "Buildkite's own request: `X-Buildkite-Event`, and either\n`X-Buildkite-Signature: timestamp=<unix s>,signature=<hex>` (HMAC-SHA256\nof `<timestamp>.<raw body>` keyed by the connection's webhook token;\nrefused when over 5 minutes off) or `X-Buildkite-Token`. Events used:\n`build.*` and `job.*` (and `ping`). Bodies up to 5 MiB. The build,\nits job and its check are written with their events before the\nanswer. Events are applied in the order Buildkite signed them (in\nwhole seconds; with a plain token, the order they arrive); a job's\nstate never moves back, and a job event's copy of a build never moves\na finished build back.\n"
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.gitpando.com/llms.txt
> Use this file to discover all available pages before exploring further.

Path: Pando API › ci

`POST /v1/integrations/buildkite/{connection}`

Buildkite's own request: `X-Buildkite-Event`, and either
`X-Buildkite-Signature: timestamp=<unix s>,signature=<hex>` (HMAC-SHA256
of `<timestamp>.<raw body>` keyed by the connection's webhook token;
refused when over 5 minutes off) or `X-Buildkite-Token`. Events used:
`build.*` and `job.*` (and `ping`). Bodies up to 5 MiB. The build,
its job and its check are written with their events before the
answer. Events are applied in the order Buildkite signed them (in
whole seconds; with a plain token, the order they arrive); a job's
state never moves back, and a job event's copy of a build never moves
a finished build back.

## Path parameters

- `buildkiteWebhook.path.connection` (string, required) — A CI connection's id: `<monorepo id>--cic_<12 hex>`.

## Example request

```json
{}
```

## Code samples

### cURL

```curl
curl --request POST \
  --url https://app.gitpando.com/v1/integrations/buildkite/string \
  --header 'Content-Type: application/json' \
  --data '{}'
```

### TypeScript

```typescript
const url = 'https://app.gitpando.com/v1/integrations/buildkite/string';
const options = {
  method: 'POST',
  headers: {'Content-Type': 'application/json'},
  body: JSON.stringify({})
};

fetch(url, options)
  .then(res => res.json())
  .then(json => console.log(json))
  .catch(err => console.error(err));
```

### Python

```python
import requests

url = "https://app.gitpando.com/v1/integrations/buildkite/string"

payload = {}
headers = {"Content-Type": "application/json"}

response = requests.post(url, json=payload, headers=headers)

print(response.text)
```

## Responses

### 200

`recorded`, or `ignored` with a reason (another monorepo's, another organization's, or a pipeline that builds no repo here).

#### Example

```json
{
  "result": "recorded",
  "reason": "string",
  "build": "string"
}
```

- `buildkiteWebhook.response.200.result` (string, required)
  - one of `"recorded"`, `"ignored"`
- `buildkiteWebhook.response.200.reason` (string, optional)
- `buildkiteWebhook.response.200.build` (string, optional) — The Pando build id.

### 401

An error

#### Example

```json
{
  "error": {
    "code": "string",
    "message": "string",
    "paths": [
      "string"
    ],
    "checks": {
      "sha": "string",
      "state": "success",
      "required": [
        "string"
      ],
      "checks_unknown": "string",
      "missing": [
        "string"
      ],
      "statuses": [
        {
          "sha": "string",
          "context": "string",
          "state": "pending",
          "target_url": "string",
          "description": "string",
          "creator": "string",
          "app": "string",
          "created_at": "2019-08-24T14:15:22Z"
        }
      ]
    }
  }
}
```

- `buildkiteWebhook.response.401.error` (object, required)
  - `buildkiteWebhook.response.401.error.code` (string, required)
  - `buildkiteWebhook.response.401.error.message` (string, required)
  - `buildkiteWebhook.response.401.error.paths` (array<string>, optional)
  - `buildkiteWebhook.response.401.error.checks` (object, optional) — GitHub's combined status, plus the required contexts and which are missing.
    - `buildkiteWebhook.response.401.error.checks.sha` (string | null, required)
    - `buildkiteWebhook.response.401.error.checks.state` (string, required) — `success` when the merge gate passes; `missing` when a required context has not reported; `unknown` while the required checks are (an unforced merge is refused).
      - one of `"success"`, `"pending"`, `"failure"`, `"error"`, `"missing"`, `"unknown"`
    - `buildkiteWebhook.response.401.error.checks.required` (array | null, required) — Null while unknown.
    - `buildkiteWebhook.response.401.error.checks.checks_unknown` (string | null, required) — Why the required checks are unknown, in plain words: "Pando couldn't read this monorepo's required checks; try again", or "pando.toml line 3: expected comma or end of structure; fix it on main, or merge with force". Null otherwise.
    - `buildkiteWebhook.response.401.error.checks.statuses` (array<object>, required) — The latest status per context.
      - `buildkiteWebhook.response.401.error.checks.statuses.sha` (string, required)
      - `buildkiteWebhook.response.401.error.checks.statuses.context` (string, required)
      - `buildkiteWebhook.response.401.error.checks.statuses.state` (string, required)
        - one of `"pending"`, `"success"`, `"failure"`, `"error"`
      - `buildkiteWebhook.response.401.error.checks.statuses.created_at` (string, required)
        - format `date-time`
      - `buildkiteWebhook.response.401.error.checks.statuses.target_url` (string | null, optional)
      - `buildkiteWebhook.response.401.error.checks.statuses.description` (string | null, optional)
      - `buildkiteWebhook.response.401.error.checks.statuses.creator` (string, optional) — The member who posted it (a login); `app:<slug>` for a status posted with a status token or by a CI integration; `hook:<hook id>` for a status token from a web hook with no app.
      - `buildkiteWebhook.response.401.error.checks.statuses.app` (string | null, optional) — The CI service that reported it (`buildkite`, `github-actions`, ...), stamped by Pando from a status token or a CI integration, never from the body or `target_url`. Null when a member posted it with their own credential. The web shows the service's mark for a slug it knows.
    - `buildkiteWebhook.response.401.error.checks.missing` (array<string>, optional)

### 404

An error

#### Example

```json
{
  "error": {
    "code": "string",
    "message": "string",
    "paths": [
      "string"
    ],
    "checks": {
      "sha": "string",
      "state": "success",
      "required": [
        "string"
      ],
      "checks_unknown": "string",
      "missing": [
        "string"
      ],
      "statuses": [
        {
          "sha": "string",
          "context": "string",
          "state": "pending",
          "target_url": "string",
          "description": "string",
          "creator": "string",
          "app": "string",
          "created_at": "2019-08-24T14:15:22Z"
        }
      ]
    }
  }
}
```

- `buildkiteWebhook.response.404.error` (object, required)
  - `buildkiteWebhook.response.404.error.code` (string, required)
  - `buildkiteWebhook.response.404.error.message` (string, required)
  - `buildkiteWebhook.response.404.error.paths` (array<string>, optional)
  - `buildkiteWebhook.response.404.error.checks` (object, optional) — GitHub's combined status, plus the required contexts and which are missing.
    - `buildkiteWebhook.response.404.error.checks.sha` (string | null, required)
    - `buildkiteWebhook.response.404.error.checks.state` (string, required) — `success` when the merge gate passes; `missing` when a required context has not reported; `unknown` while the required checks are (an unforced merge is refused).
      - one of `"success"`, `"pending"`, `"failure"`, `"error"`, `"missing"`, `"unknown"`
    - `buildkiteWebhook.response.404.error.checks.required` (array | null, required) — Null while unknown.
    - `buildkiteWebhook.response.404.error.checks.checks_unknown` (string | null, required) — Why the required checks are unknown, in plain words: "Pando couldn't read this monorepo's required checks; try again", or "pando.toml line 3: expected comma or end of structure; fix it on main, or merge with force". Null otherwise.
    - `buildkiteWebhook.response.404.error.checks.statuses` (array<object>, required) — The latest status per context.
      - `buildkiteWebhook.response.404.error.checks.statuses.sha` (string, required)
      - `buildkiteWebhook.response.404.error.checks.statuses.context` (string, required)
      - `buildkiteWebhook.response.404.error.checks.statuses.state` (string, required)
        - one of `"pending"`, `"success"`, `"failure"`, `"error"`
      - `buildkiteWebhook.response.404.error.checks.statuses.created_at` (string, required)
        - format `date-time`
      - `buildkiteWebhook.response.404.error.checks.statuses.target_url` (string | null, optional)
      - `buildkiteWebhook.response.404.error.checks.statuses.description` (string | null, optional)
      - `buildkiteWebhook.response.404.error.checks.statuses.creator` (string, optional) — The member who posted it (a login); `app:<slug>` for a status posted with a status token or by a CI integration; `hook:<hook id>` for a status token from a web hook with no app.
      - `buildkiteWebhook.response.404.error.checks.statuses.app` (string | null, optional) — The CI service that reported it (`buildkite`, `github-actions`, ...), stamped by Pando from a status token or a CI integration, never from the body or `target_url`. Null when a member posted it with their own credential. The web shows the service's mark for a slug it knows.
    - `buildkiteWebhook.response.404.error.checks.missing` (array<string>, optional)

### 413

An error

#### Example

```json
{
  "error": {
    "code": "string",
    "message": "string",
    "paths": [
      "string"
    ],
    "checks": {
      "sha": "string",
      "state": "success",
      "required": [
        "string"
      ],
      "checks_unknown": "string",
      "missing": [
        "string"
      ],
      "statuses": [
        {
          "sha": "string",
          "context": "string",
          "state": "pending",
          "target_url": "string",
          "description": "string",
          "creator": "string",
          "app": "string",
          "created_at": "2019-08-24T14:15:22Z"
        }
      ]
    }
  }
}
```

- `buildkiteWebhook.response.413.error` (object, required)
  - `buildkiteWebhook.response.413.error.code` (string, required)
  - `buildkiteWebhook.response.413.error.message` (string, required)
  - `buildkiteWebhook.response.413.error.paths` (array<string>, optional)
  - `buildkiteWebhook.response.413.error.checks` (object, optional) — GitHub's combined status, plus the required contexts and which are missing.
    - `buildkiteWebhook.response.413.error.checks.sha` (string | null, required)
    - `buildkiteWebhook.response.413.error.checks.state` (string, required) — `success` when the merge gate passes; `missing` when a required context has not reported; `unknown` while the required checks are (an unforced merge is refused).
      - one of `"success"`, `"pending"`, `"failure"`, `"error"`, `"missing"`, `"unknown"`
    - `buildkiteWebhook.response.413.error.checks.required` (array | null, required) — Null while unknown.
    - `buildkiteWebhook.response.413.error.checks.checks_unknown` (string | null, required) — Why the required checks are unknown, in plain words: "Pando couldn't read this monorepo's required checks; try again", or "pando.toml line 3: expected comma or end of structure; fix it on main, or merge with force". Null otherwise.
    - `buildkiteWebhook.response.413.error.checks.statuses` (array<object>, required) — The latest status per context.
      - `buildkiteWebhook.response.413.error.checks.statuses.sha` (string, required)
      - `buildkiteWebhook.response.413.error.checks.statuses.context` (string, required)
      - `buildkiteWebhook.response.413.error.checks.statuses.state` (string, required)
        - one of `"pending"`, `"success"`, `"failure"`, `"error"`
      - `buildkiteWebhook.response.413.error.checks.statuses.created_at` (string, required)
        - format `date-time`
      - `buildkiteWebhook.response.413.error.checks.statuses.target_url` (string | null, optional)
      - `buildkiteWebhook.response.413.error.checks.statuses.description` (string | null, optional)
      - `buildkiteWebhook.response.413.error.checks.statuses.creator` (string, optional) — The member who posted it (a login); `app:<slug>` for a status posted with a status token or by a CI integration; `hook:<hook id>` for a status token from a web hook with no app.
      - `buildkiteWebhook.response.413.error.checks.statuses.app` (string | null, optional) — The CI service that reported it (`buildkite`, `github-actions`, ...), stamped by Pando from a status token or a CI integration, never from the body or `target_url`. Null when a member posted it with their own credential. The web shows the service's mark for a slug it knows.
    - `buildkiteWebhook.response.413.error.checks.missing` (array<string>, optional)


Source: https://docs.gitpando.com/api/ci/buildkiteWebhook/index.md