Skip to content
Error codes · realuptime errors ingest

RU-4002: Ingest key revoked

The ingest key in the URL was revoked. Unlike agent tokens, ingest keys are designed to be public, so revocation refuses loudly: `reason: "key_revoked"`: and SDKs log it once and disable themselves instead of retrying into a black hole.

Where it is raised

  • Errors ingest (/api/errors/v1/ingest)
  • Errors feedback (/api/errors/v1/feedback)
  • Scrub rules (/api/errors/v1/scrub-rules) (shorter message)
  • Source map upload, POST /api/errors/v1/sourcemaps/<key>

What triggers it

The key is looked up before any budget is spent, and a key found with a revoked state answers here. A key that does not exist at all answers a plain 404. That asymmetry is deliberate: a revoked key was real, so the SDK is told to stop.

Example response

POST /api/errors/v1/ingest/<key>
HTTP 403

{
  "error": "This ingest key has been revoked. Rotate it in realuptime Errors settings.",
  "reason": "key_revoked",
  "code": "RU-4002"
}

Common causes

  • The key was rotated in realuptime Errors settings and old deploys still carry the previous key.
  • A key was revoked deliberately after being abused.

How to fix it

  1. Get the current ingest key from realuptime Errors settings.
  2. Redeploy every app and mobile build that embeds the old key.