Where it is raised
- Checks: 6 routes
- Status Pages: 6 routes
- Notification Channels: 4 routes
- Incidents: 2 routes
- Maintenance: 2 routes
- Errors: 3 routes
- Agents: 3 routes
- Keyed MCP endpoint, for every tool that creates, changes or deletes something
What triggers it
The write gate runs right after authentication and before the request body is parsed. A key whose permission is not read_write is stopped there on every route that changes data. A key that carries resource scopes is judged by RU-1008 instead, so this code only appears for keys with no scopes.
Example response
POST /api/v1/checks
HTTP 403
{
"error": "This API key is read-only. Generate a read-write key to perform this action.",
"code": "RU-1004",
"docs": "https://realuptime.io/kb/errors/ru-1004"
}Common causes
- The key was created as read-only on purpose and is now being used for a write.
- A read-write key was expected but a different key was configured.
How to fix it
- Generate a read-write key from your dashboard's API & MCP access section.
- Use the read-write key for mutating calls; keep read-only keys for dashboards and integrations that only read.