Errors
Cargobase APIs use standard HTTP status codes—read the body, then decide whether to retry, fix the request, or escalate.
Failed requests return standard HTTP status codes. The shape of the error body varies by collection; check the response schemas on the operation you called for the fields you can rely on.
Common statuses
| Status | Meaning |
|---|---|
400 | Validation failed or the request was malformed |
401 / 403 | Missing, invalid, or insufficient credentials |
404 | Unknown resource, or the wrong environment |
409 | Conflict with the resource’s current state |
429 | Rate limited—retry with backoff |
5xx | Server-side failure—retry, then contact Support if it persists |
Debugging tips
- Confirm the base URL and token belong to the same environment.
- Compare your payload to the example and schema in the reference—required fields and enums are the usual culprits.
- For a
400, paste the payload and the error response into the Payload Doctor. It shows which fields the API rejects and how to fix them. It currently covers Post carrier tracking update. - Log the response body and
request_id(when present) before opening a support ticket.