webhook_endpoint_limit_reached
- HTTP status
- 409
- Retry
- No
- Execution
- Nothing was done
- Admin needed
- No
Webhook endpoint limit reached. Each workspace can have a limited number of webhook endpoints per mode (test and live counted separately).
What it means
The API returns HTTP 409 with error.code set to webhook_endpoint_limit_reached. The default message is: "This workspace already has the maximum number of webhook endpoints for this mode."
Common causes
- The limit in
details.limitwas reached.
How to identify it
Check the response status (409) and error.code (webhook_endpoint_limit_reached). Branch on error.code, not on the message text: messages can be reworded, codes do not change within v1. Log error.request_id (also sent as the X-Request-Id header) so support can find the request.
How to fix it
- Delete an endpoint you no longer use, or subscribe one endpoint to more event types.
Retry guidance
Sending the request unchanged fails the same way. Fix the cause first (see How to fix it), then send it again.
Did anything happen?
This request was refused before any call was placed and before anything was charged.
Idempotency
Nothing was done and the refusal is not stored under the Idempotency-Key. Fix the cause, then send the same request (with the same key if you sent one).
Who can fix it
The developer who sends the request can fix it; no administrator action is normally needed.
When to contact support
If the error persists after the steps above, contact support@relationsai.com. See Support for what to include (the request_id, the time in UTC, the operation, and whether you used a test or live key) and what never to send (API keys, Authorization headers, webhook signing secrets, recording links, transcripts or customer data).
Example error response
JSON
Operations that can return this error
POST /webhook-endpoints: Create a webhook endpoint
See all codes in the error-code reference.