Error Codes
401 Unauthorized
Can occur in the following cases:
- No Bearer token was sent
- The token is invalid
- The token has expired
Call the POST /api/public/auth/token endpoint again to get a new token.
403 Forbidden
Can occur in the following cases:
- The user is not connecting from an IP address allowed for this tenant
- An IP restriction is active on the Public API side
If an IP restriction is active, you need to share your outbound IP address with our team. Static IPs and CIDR notation are accepted:
85.100.10.25
85.100.10.0/24429 Too Many Requests
With the default configuration, a per-tenant rate limit applies: 40 requests / 60 seconds. The limit for the token endpoint (/api/public/auth/token) is lower: 5 requests / 60 seconds (per client IP address).
Wait for the duration given in the Retry-After response header, then try again.
400 Bad Request
Occurs with invalid credentials or a malformed OAuth request.
| Error Code | Description |
|---|---|
invalid_grant | Invalid username or password |
invalid_request | Malformed request |
For high-volume integrations, rate limits can be reviewed by our team.
400 Validation Error
On endpoints such as Call Records, if the request body is invalid (for example, startTime is later than endTime, take exceeds the allowed maximum, or a date format is wrong), a standard error body is returned that indicates which field is invalid:
In validationErrors, the members field gives the invalid field name and the message field gives the reason.
403 Business Rule Error
Requests that pass validation but violate a business rule (for example, an assistantId that cannot be found, a callId that cannot be found, or a recording that cannot be retrieved from the provider) return 403. The body has the following form; the reason is given in the message field and, when available, the error type in the code field.
404 Not Found
Returned by the Call Recording and Call Ingestion (recording upload) endpoints when the specified call cannot be found. Call IDs that belong to another company are also reported as “not found”.
Error Format on Call Ingestion Endpoints
Unlike the formats above, errors on the /api/v1/webhooks/* endpoints are returned as { "success": false, "message": "..." }. See the Call Ingestion and Text Channels sections for details.