Uptimely

invalid_token

HTTP 401 — Invalid access token

invalid_token means the Bearer credential is not a valid Uptimely API key and could not be verified as an access token, so the request was refused.

What it means

The Bearer credential is not shaped like an Uptimely API key and could not be verified as an access token. Any such value gets this answer, including a garbled or random string. A valid OAuth access token gets unsupported_credential_type instead.

Common causes

  • The value is not an Uptimely API key at all (a typo, a placeholder or a garbled string).
  • An access token that has expired or whose grant was revoked under Settings → Connected AI apps.

How to fix it

Send a project API key (`uptimely_live_…`) as the Bearer credential. If you meant to send an access token, obtain a fresh one through the flow that issued it.

Should you retry?

Only after obtaining a fresh token.

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: