Where it is raised
GET /api/v1/errors/projectsPOST /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
What triggers it
Every Errors API route first checks that the account has the Errors product and stops there when it does not, before validating anything else. It is the first check after the write gate on project, issue and release routes.
Example response
POST /api/v1/errors/projects
HTTP 403
{
"error": "This account does not have RealUptime Errors.",
"code": "RU-4005"
}Common causes
- The account never added the errors product.
- The errors product was removed from the account.
How to fix it
- Add realuptime errors to your account from the dashboard's products section.
- Retry once the product shows as active.