Webhooks
DELETE/v1/webhooks/endpoints/{id}
Remove an endpoint and its delivery history
The history goes with it. To stop deliveries but keep the record — a planned maintenance, say — PATCH the endpoint to DISABLED instead.
- Auth
- API key
- Scope
- webhooks:manage
- Rate limit
- DEFAULT
- Search quota
- Free
- Idempotency
- Not required
Path parameters
Responses
204
Removed. Deliveries already recorded stay in the history — deleting the endpoint does not erase what we tried to send you.
Errors
Every one of these carries the same envelope. What each error.type means, and whether a retry can succeed, is on the error index — once, for all operations.
Response headers
Set on every response of this operation, successful or not.
Example
curl -sS -X DELETE "$VACABEE_API_URL/v1/webhooks/endpoints/<id>" \
-H "Authorization: Bearer $VACABEE_API_KEY"Set VACABEE_API_URL to https://api.vacabee.com with a live key, or to https://sandbox-api.vacabee.com with a vcb_test_ key. Binding a host to one kind of key is planned and is not enforced by the host yet, so nothing stops a key from being answered at the wrong base URL — assert the prefix against your configured URL yourself. What the sandbox answers
TypeScript SDK
await vacabee.webhooks.remove(…);The typed method sends the right headers, derives the idempotency key where one is required, and returns the response type generated from this document. Installing and using the SDK

