Skip to content

API reference

Delete webhook

webhooks.DeleteWebhookWriteAPI key

Delete a webhook subscription and stop further deliveries to its endpoint.

POST/v1/operations/webhooks.DeleteWebhook
On this page

Access & visibility

Allow webhooks.DeleteWebhook on your API key.

Workspace access by default. Private member data requires approved member delegation through Brigg-Act-As; the key supplies permissions while private ownership and project boundaries remain enforced.

Set up authentication · Choose permissions

Request fields

Send a JSON object with the following fields. Required fields must be included; omit optional fields you do not need.

idstringRequired

Use the subscription id returned by ListWebhooks. It is not an event ID, delivery ID or signing secret. webhooks.ListWebhooks.

At least 1 character.

Stop a subscription

Find the subscription in List webhooks and send its id. This removes the subscription; it does not undo changes already delivered to your endpoint. Pending delivery work checks whether the subscription still exists and skips deleted subscriptions. A request already in flight can still reach your endpoint.

Deletion has no public undo operation. If you need the stream again, prepare a new subscription and obtain administrator approval. A fresh delete of an absent subscription returns 404 not_found; retrying a successful original request with the same idempotency key replays its original result. The deleted subscription is no longer available for event recovery or replay.

Response

Returns 200 OK with a JSON body.

okbooleanRequired

Whether the action completed successfully.

Errors & retries

Set BRIGG_REQUEST_ID once for each logical action. The samples send it as Idempotency-Key. Reuse the same value and body on retries, including after a timeout; a missing response does not prove the action failed.

For rate limits, follow the server’s retry guidance and back off. See HTTP errors and safe retries and limits.

HTTP status Code What to do
400 invalid_json Send a JSON object with Content-Type: application/json.
400 invalid_input Check the request fields and types. Supply a stable Idempotency-Key containing 1–200 characters.
401 invalid_key The workspace API key is missing, invalid or revoked.
403 forbidden Check the key’s operation and resource grants. If Brigg-Act-As is supplied, the key must be authorized to delegate to that member.
404 not_found The requested operation or resource is not available to this credential.
429 rate_limited Wait for Retry-After before retrying. Reuse the original Idempotency-Key.

Next steps

Download OpenAPI · Versioning & retirement

JSON schemas

Use the complete schemas for validation or client generation.

Full request JSON schema
{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "minLength": 1,
      "description": "Use the subscription id returned by ListWebhooks. It is not an event ID, delivery ID or signing secret. [webhooks.ListWebhooks](/developers/reference/webhooks/ListWebhooks)."
    }
  },
  "required": [
    "id"
  ],
  "additionalProperties": false,
  "examples": [
    {
      "id": "wh_company_changes"
    }
  ]
}
Full response JSON schema
{
  "type": "object",
  "properties": {
    "ok": {
      "type": "boolean",
      "description": "Whether the action completed successfully."
    }
  },
  "required": [
    "ok"
  ],
  "additionalProperties": false,
  "examples": [
    {
      "ok": true
    }
  ]
}

Search by operation name or what you want to build.

Use arrow keys to browse. Enter opens a result.