Errors
Every endpoint follows standard HTTP status semantics. This page explains what each status means for a Sovereign Solutions API call and what to check first.
A full, per-endpoint error-code reference (application-level codes and messages, beyond the HTTP status) is not yet published on this site. If you've hit an error response whose shape isn't covered by the general guidance below, reach support with the endpoint, request body, and the full response - we'll get you an answer and add it here.
HTTP status codes
| Status | Meaning | Check first |
|---|---|---|
200 OK | Request succeeded | - |
400 Bad Request | Request body or parameters are malformed | Validate required fields and types against the API Reference for that endpoint |
401 Unauthorized | Missing or invalid api-key, or - on tenant APIs - a missing or expired bearer token | Check the api-key query parameter; on tenant APIs re-issue a token via Authentication - tokens expire (expires_in in the token response) |
403 Forbidden | Valid token, but not permitted for this resource | Confirm your api-key matches the tenant you're calling, and that the endpoint doesn't require a tenant you haven't been provisioned |
404 Not Found | Resource doesn't exist, or the path is wrong | Check the endpoint path and any path parameters (e.g. a record ID) |
429 Too Many Requests | Rate limit exceeded | See Rate Limits; back off and retry |
5xx | Server-side error | Retry with backoff; if it persists, contact support with a request ID or timestamp |
Required credentials
A missing or malformed credential is the most common cause of a 401. What a call needs depends on
the API - every operation states it in its Auth line:
| API | Credentials |
|---|---|
| API key only (location, map and route APIs, and the token call) | ?api-key=<apiKey> |
| Requires Intelomatic tenant (employees, customers, plans, visits, tracking, events, data layers) | Authorization: Bearer <access_token> and ?api-key=<apiKey> |
See Authentication for how to obtain a token.
Search and pagination responses
Search endpoints wrap results in a consistent envelope - if you're getting an empty data array
instead of an error, check skip/take in your request body rather than assuming a failure:
{
"data": [],
"total": 0
}
Still stuck?
Contact support with the endpoint, your request body (redact credentials), and the full response body and status code.
