---
search:
  tags:
    - Webhooks
    - POST
seo:
  description: >-
    Create a webhook. Reference for the POST /webhooks endpoint in the
    BillionSend API.
sidebar:
  label: Create a webhook
  badge: POST
title: Create a webhook
type: openapi-operation
---
`POST /webhooks`

**Request body** (`application/json`, required)

- `endpoint` (string<uri>, required)
- `events` (string[], required)
- `inbox_ids` (string<uuid>[] | null) — BillionSend extension: inbox events and email.received reach this endpoint only for these inboxes of the team (at most 100). null means every inbox. Omitted: every inbox.
- `signing_secret` (string) — Signing secret to use instead of minting one: whsec\_ followed by base64 of 24-64 bytes (the Standard Webhooks format). An existing secret carried over keeps the receiver verifying unchanged; when omitted, a new one is generated.

Request body example:

```json
{
  "endpoint": "http://example.com",
  "events": [
    "email.scheduled"
  ],
  "inbox_ids": [
    "497f6eca-6276-4993-bfeb-53cbbbba6f08"
  ],
  "signing_secret": "string"
}
```

**Responses**

- `200` — Webhook created; signing\_secret is also retrievable via GET /webhooks/{id}
- `401` — Missing, malformed, unknown or revoked API key
- `403` — Plan webhook endpoint limit reached
- `422` — Validation error
- `429` — Over the rate limit (rate\_limit\_exceeded, with Retry-After)

Response example, 200:

```json
{
  "object": "webhook",
  "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
  "signing_secret": "string"
}
```
