Skip to main content
Every error returned by the Xobito API follows a consistent shape. Use the HTTP status for classification and the message (and optional errors) for detail.

Error envelope

429 rate-limit responses use a different shape — see Rate Limits.

HTTP statuses

400 Bad Request

Returned when the subdomain path segment is invalid.

401 Unauthorized

The token is missing or not recognised. Missing header:
Invalid / revoked / expired token:

403 Forbidden

Missing ability (scope):
The ability name in the message matches exactly the scope the endpoint requires. Plan limit exceeded (e.g. max contacts for the workspace plan):

404 Not Found

The resource does not exist (or does not belong to your workspace).
The resource name in the message varies by endpoint (Contact not found, Status not found, Template not found, etc.).

422 Unprocessable Entity

Validation failed. The errors object maps field names to an array of human-readable messages.

429 Too Many Requests

Rate limit exceeded. See Rate Limits.

500 Internal Server Error

Something broke on Xobito’s side. The message describes the failed action.
Retry after a short delay. If the error persists, contact support.

Handling errors

Common mistakes

The Authorization header was missing. It must be exactly Authorization: Bearer <your_token> (64-character hex string, no prefix).
Your token is valid but lacks the specific ability. Regenerate a new token in Settings → API Management with the ability the endpoint requires.
The {subdomain} in the URL path does not match any workspace. Check the path: https://dash.xobito.com/api/v1/{subdomain}/....
Either the template does not exist, does not belong to your workspace, or is not yet APPROVED by Meta. Only APPROVED templates can be sent.