Skip to content
Error codes · Authentication & API keys

RU-1001: Missing API credentials

The request reached an authenticated endpoint without an Authorization header, so realuptime could not tell whose request it was.

On the wire

Ships with HTTP status 401, carrying "code": "RU-1001" in the response body alongside the human-readable error message. Existing fields are never replaced by the code: it is additive.

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

  1. Generate an API key from your dashboard's API & MCP access section if you don't have one.
  2. Send it as `Authorization: Bearer <api key>` on every request.
  3. If you use a proxy or gateway, confirm it forwards the Authorization header.

Related codes

  • RU-1002: Invalid or revoked API key
  • RU-1003: API access requires a paid plan

Still stuck?

Ask support and mention RU-1001: the code pins down the exact refusal path, so you skip the diagnostic back-and-forth.