internal_error
HTTP 500 — Internal server error
internal_error means something failed on Uptimely's side while handling the request, which may or may not have taken effect.
What it means
Something failed on Uptimely's side. The request may or may not have taken effect.
Common causes
- A transient server-side failure.
How to fix it
Retry safe requests with backoff. For POSTs, retry ONLY with the same `Idempotency-Key` so a request that did take effect is replayed, not repeated. If it persists, contact support with the `request_id` from the response.
Should you retry?
Yes — with backoff, and with the same idempotency key on writes.
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 credentialsinvalid_api_key— HTTP 401, Invalid API keyinvalid_token— HTTP 401, Invalid access tokenunsupported_credential_type— HTTP 403, Credential type not usable on this surfaceinsufficient_scope— HTTP 403, Insufficient scopefeature_not_enabled— HTTP 403, Feature not enabled on this planvalidation_failed— HTTP 400, Request validation failedresource_not_found— HTTP 404, Resource not foundrate_limited— HTTP 429, Rate limit exceededquota_exhausted— HTTP 429, Plan quota exhaustedidempotency_key_reused— HTTP 422, Idempotency-Key reused with a different requestidempotency_in_progress— HTTP 409, A request with this Idempotency-Key is still in progress