Skip to Content

Scopes

API key scopes control which operations a key can perform. Scopes are assigned when creating an API key and determine whether the key can read, write, or delete checks.

Available Scopes

ScopeDescription
checks:readList checks, get check details, history, and stats
checks:writeCreate, update, and toggle checks
checks:deleteDelete checks

Default Scope

API keys created without specifying scopes default to checks:read only. This means existing keys are read-only and cannot modify your checks.

Scope Requirements by Endpoint

EndpointMethodRequired Scope
/v1/public/checksGETchecks:read
/v1/public/checks/{id}GETchecks:read
/v1/public/checks/{id}/historyGETchecks:read
/v1/public/checks/{id}/statsGETchecks:read
/v1/public/checksPOSTchecks:write
/v1/public/checks/{id}PATCHchecks:write
/v1/public/checks/{id}/togglePOSTchecks:write
/v1/public/checks/{id}DELETEchecks:delete

Error Response

If your API key does not have the required scope, the API returns a 403 Forbidden:

{ "error": "API key does not have the required scope: checks:write" }

Creating a Scoped Key

When creating an API key in Settings > API, select the scopes you need. You can assign multiple scopes to a single key.

For full CRUD access, enable all three scopes: checks:read, checks:write, and checks:delete.

Last updated on