Public API errors (RFC 7807)
How InboxOps Problem Details work, request correlation, and links to each stable error code used in type URIs.
Public API errors (RFC 7807)
InboxOps /api/v1 error responses use RFC 7807 Problem Details with Content-Type: application/problem+json.
Each response includes a stable machine identifier in code, and URIs in type (and usually instance) under https://docs.inboxops.app/api/problems/. Those URLs resolve to the pages in this section so humans and tools can look up what each identifier means.
For authentication, limits, idempotency, and OpenAPI, see Public API.
Fields
| Field | Role |
|---|---|
type | URI identifying the error kind. Last path segment equals code (for example …/unauthorized). |
title | Short human title (may vary slightly; prefer code + status for logic). |
status | HTTP status code. |
detail | Specific explanation for this request. |
code | Stable string for programmatic handling (matches the last segment of type). |
instance | When present, pairs with X-Request-Id — see Instance URIs. |
Error codes
| HTTP | code | Page |
|---|---|---|
| 400 | bad_request | Bad request |
| 401 | unauthorized | Unauthorized |
| 403 | forbidden | Forbidden |
| 403 | insufficient_scope | Insufficient scope |
| 404 | not_found | Not found |
| 405 | method_not_allowed | Method not allowed |
| 409 | conflict | Conflict |
| 409 | idempotency_conflict | Idempotency conflict |
| 429 | rate_limit_exceeded | Rate limit exceeded |
| 500 | internal_error | Internal error |
| 503 | service_unavailable | Service unavailable |
If you see a code that is not listed here, treat status and detail as authoritative and contact InboxOps support with X-Request-Id.
Was this page helpful?
Last updated 3 weeks ago
Built with Documentation.AI