Skip to content
Error codes · Authentication & API keys

RU-1008: API key is not scoped to this resource

The key is valid, but it carries resource-scoped grants (REA-475) and this request's resource (monitors, status pages, errors, or account configuration) is either absent from its grants or granted at a lower level (read) than the request needs (read_write). A legacy key with no resource scoping is never affected by this check; its permission applies to every resource.

On the wire

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

Common causes

  • A resource-scoped key was created for one product line (say, monitors) and used against another (say, status pages).
  • A resource-scoped key was granted read on a resource and the caller attempted a write.

How to fix it

  1. In the dashboard's API & MCP access section, open the key's menu and add or widen the grant for the resource this request needs.
  2. Or generate a legacy global-scope key if the integration needs every resource.

Related codes

Still stuck?

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