Where it is raised
- Checks: 14 routes
- Metrics: 1 route
- Status Pages: 11 routes
- Notification Channels: 6 routes
- Incidents: 4 routes
- Maintenance: 3 routes
- Errors: 8 routes
- Agents: 6 routes
- Keyed MCP endpoint, same status and body
What triggers it
The Authorization header is absent, does not start with Bearer, or has nothing after it. The check runs after the per-address failure limiter and before any key lookup, and each refusal counts toward that limiter, which is why a client looping without a key ends on RU-2001.
Example response
GET /api/v1/checks
HTTP 401
{
"error": "Missing Authorization: Bearer <api key> header.",
"code": "RU-1001",
"docs": "https://realuptime.io/kb/errors/ru-1001"
}Common causes
- The Authorization header was never set, or was stripped by a proxy.
- The header is present but not in the required `Bearer <api key>` form.
- The key was placed in a query parameter or request body instead of the header.
How to fix it
- Generate an API key from your dashboard's API & MCP access section if you don't have one.
- Send it as `Authorization: Bearer <api key>` on every request.
- If you use a proxy or gateway, confirm it forwards the Authorization header.