missing_credentials

What it means

The request reached /v1 without any credential. Every /v1 endpoint requires a project API key.

Common causes

• No Authorization header was sent.
• The header name or shape is wrong — the API reads `Authorization: Bearer <key>` and nothing else (no query-string keys, no cookies).

How to fix it

Send your key as `Authorization: Bearer uptimely_live_…`. Create one under Settings → API Keys → Public API keys in your Uptimely project.

Should you retry?

No — the same request will fail the same way until a credential is added.

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:

• invalid_api_key — HTTP 401, Invalid API key
• 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