Problems Overview
When a /v2 request fails, the API returns an HTTP status code and an error body. The body follows RFC 9457, so every failure has the same shape, whatever the cause.
Problems are grouped by type. Each type has a stable URI, https://docs.mure.app/problems/<slug>, and its own page in this section. The URI names the problem type, not the failed request, so it is the same in sandbox, production, and local.
How to read a problem page
Each page starts with the values the API uses for that problem type:
| Field | Meaning |
|---|---|
type | The stable URI for the problem type. On a problem page, this link points at the page you are reading. |
title | A short summary of the type, such as "Rate limited". The same title appears for every occurrence. |
status | The HTTP status code returned with the problem. |
details | The extra fields in the details object, when the problem has any. none means the problem has no extra fields. |
Below the table, What to do explains how to recover. For example, honor the Retry-After header, fix the field named in the error, or retry later.
For the full error body, including detail, instance, and correlationId, see Error Handling. That page also lists every problem type with its status and meaning.
Problem types
- Bad request
- Missing API key
- Invalid API key
- Chain not allowed for key environment
- Rate limited
- Route not found
- Transfer not found
- Validation failed
- Transfer service failure
- Token registry service failure
- Upstream failure
- Internal error