Errors and request references
The error body every REST endpoint returns, what the status codes mean, and how to trace a failed call with its request reference.
Every REST error answers with the same JSON body:
{
"detail": "Unauthorized",
"hint": "Sign in again to continue.",
"retryable": false,
"request_id": "64b9802f04d348ae88b698192076f425"
}Field | Meaning |
|---|---|
| What went wrong, in plain words, safe to show to a person |
| A stable code you can branch on (for example |
| What to do about it |
|
|
| The reference of this request |
| Present when a plan feature or a policy refused the call |
A 422 (validation) answers {"detail": [...]} with one entry per field, naming the field and the problem.
Status codes
Status | Meaning |
|---|---|
| The request cannot be done as asked (for example a job that is already running) |
| No token, or an unknown, expired or revoked one |
| Allowed for nobody in your position: your role, the token's binding, your plan, or a policy |
| Does not exist, or you may not know it exists |
| Conflicts with the current state (for example held by a release rule) |
| The body does not match the schema |
| Too many attempts; wait and try again |
| Our fault; |
Tracing a failed call
Every answer carries its reference. In the console, Activity > Requests, search the request_id: you see its audit entries in order and the work it started. Support can find the same request from the reference alone; quote it when you write to support@remplatforms.com. Over MCP, the tool error_find_reference does the same, and error_explain explains any code.