invalid_api_key

What it means

A Bearer credential was presented, but it does not match any active API key.

Common causes

• The key was revoked in Settings → API Keys.
• The key was mistyped or truncated when copied (keys are shown once at creation).
• The key belongs to a different Uptimely deployment or environment.

How to fix it

Create a new key under Settings → API Keys → Public API keys and replace the stored credential. Keys are hashed at rest — a lost key cannot be recovered, only replaced.

Should you retry?

No — replace the credential first.

The response shape

Every /v1 error is an RFC 9457 application/problem+json document: type links to this page, code is the stable value to branch on (never parse title or detail), and request_id identifies the request to support. Validation failures add an errors array of per-field JSON pointers.

API overview · API reference · All error codes:

• missing_credentials — HTTP 401, Missing credentials
• invalid_token — HTTP 401, Invalid access token
• unsupported_credential_type — HTTP 403, Credential type not usable on this surface
• insufficient_scope — HTTP 403, Insufficient scope
• feature_not_enabled — HTTP 403, Feature not enabled on this plan
• validation_failed — HTTP 400, Request validation failed
• resource_not_found — HTTP 404, Resource not found
• rate_limited — HTTP 429, Rate limit exceeded
• quota_exhausted — HTTP 429, Plan quota exhausted
• idempotency_key_reused — HTTP 422, Idempotency-Key reused with a different request
• idempotency_in_progress — HTTP 409, A request with this Idempotency-Key is still in progress
• internal_error — HTTP 500, Internal server error