Manage webhook endpoints over the API
Webhook endpoint CRUD is now documented in the OpenAPI spec — create, list, fetch, update, and delete endpoints programmatically. The endpoints themselves shipped earlier; today we backfilled the docs and SDKs.
The /webhook-endpoints family of endpoints is live in the v1 API and now appears in the API reference alongside properties, site visits, and action items. Five operations:
- GET /v1/webhook-endpoints — list your endpoints
- POST /v1/webhook-endpoints — create one (returns the signing secret once)
- GET /v1/webhook-endpoints/{id} — fetch a single endpoint
- PATCH /v1/webhook-endpoints/{id} — update name / URL / events / disabled
- DELETE /v1/webhook-endpoints/{id} — remove it
Same bearer-auth as the rest of the v1 API, idempotency keys on writes, and the standard error envelope. SDK regeneration off the spec picks up these endpoints automatically.