Skip to content
Error codes · Authentication & API keys

RU-1002: Invalid or revoked API key

An Authorization header was present, but the key it carried does not match any live API key. realuptime deliberately does not say which of invalid, revoked or expired applies.

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

One reply covers three lookups: the key's hash matches no live key, the key was revoked, or the account behind it no longer exists. The body never says which one. Every refusal is recorded as a failed attempt against the caller's address.

Example response

GET /api/v1/checks
HTTP 401

{
  "error": "Invalid or revoked API key.",
  "code": "RU-1002",
  "docs": "https://realuptime.io/kb/errors/ru-1002"
}

Common causes

  • The key was revoked from the dashboard.
  • The key reached an expiry date set on it, after which it is refused exactly as a revoked key is.
  • The key was mistyped, truncated, or had whitespace added when copied.
  • The key belongs to a deleted account.

How to fix it

  1. Check the key against the API & MCP access section of your dashboard.
  2. If the key was revoked, generate a new one and update every consumer.
  3. If the key expired, give it a new expiry date from its row menu, or generate a replacement.
  4. Repeated failures from one address are rate limited: fix the key before retrying in a loop.

Related codes