Where it is raised
POST /api/v1/errors/projectsGET /api/v1/errors/projects/{id}GET /api/v1/errors/projects/{id}/issuesGET /api/v1/errors/issues/{id}PATCH /api/v1/errors/issues/{id}POST /api/v1/errors/releases
- Keyed MCP endpoint, Errors tools
What triggers it
Path ids are checked as UUIDs before any lookup, project names must be 1 to 120 characters, and the release route names invalid fields by their schema name. A previousRelease equal to the release being registered is refused here too.
Example response
GET /api/v1/errors/issues/{id}
HTTP 400
{
"error": "issueId must be a valid UUID.",
"code": "RU-4007"
}Common causes
- An ID that is not a valid UUID.
- A query parameter outside its allowed range.
- A request body that is not JSON, names a field the endpoint does not read, or sends a `status` other than open, resolved or ignored.
How to fix it
- Fix the parameter named in the `error` field, then resend.
- Copy IDs from API list responses rather than constructing them.
- Send exactly the fields the endpoint documents. To reopen an issue, send `status: "open"`.