Where it is raised
GET /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
The project, issue or release is looked up inside the caller's account. For a release the message is No errors project with that ID exists in this account. A project id that is not a UUID is a RU-4007 refusal first.
Example response
GET /api/v1/errors/projects/{id}
HTTP 404
{
"error": "Project not found.",
"code": "RU-4006"
}Common causes
- The project or issue was deleted.
- The ID belongs to a different account.
- A typo in the ID.
How to fix it
- List your projects (GET /api/v1/errors/projects) and confirm the ID.
- Confirm the API key belongs to the account that owns the resource.