unsupported_credential_type

What it means

The credential is valid, but this surface does not accept its type. /v1 accepts project API keys only — OAuth access tokens are user-level with no project binding, while every /v1 resource is project-scoped.

Common causes

• An OAuth access token (minted for MCP/AI-agent access) was sent to a /v1 endpoint.

How to fix it

Use a project API key (`uptimely_live_…`) for /v1. OAuth tokens keep working on the MCP surface they were issued for.

Should you retry?

No — switch credential types 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_api_key — HTTP 401, Invalid API key
• invalid_token — HTTP 401, Invalid access token
• 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