Uptimely Authentication

generated: '2026-11-10'
method: searched
generator: extract-docs-artifacts.py (local)
source: https://getuptimely.com/docs/api
sources:
- https://getuptimely.com/docs/api
- https://getuptimely.com/docs/api-reference/webhooks/rotateWebhookEndpointSecret
- https://getuptimely.com/docs/getting-started
- https://getuptimely.com/agent-setup/prompt.md
description: Authentication methods published for Uptimely APIs
schemes:
- type: http-bearer
  name: Public REST API
  evidence: 'Create a key under Settings → API Keys → Public API keys in your project (keys are shown once and stored hashed), then send it as
    a Bearer token: curl https://app.getuptimely.com/v1/monitors \ -H "Authorization: Bearer $UPTIMELY_API_KEY "'
  location: header
  header: Authorization
  how_to_obtain: Create a public API key in the project Settings → API Keys → Public API keys page.
- type: http-bearer
  name: Prometheus scrape endpoint
  evidence: 'It authenticates with a legacy project API key (the "API Keys" card under Settings → API Keys, below the public keys — the same key
    class the MCP tools take), sent as Authorization: Bearer … .'
  location: header
  header: Authorization
  how_to_obtain: Create a legacy project API key in Settings → API Keys.
- type: apiKey
  name: OpenTelemetry ingestion
  evidence: Authenticate with a telemetry ingestion key in the x-uptimely-ingestion-key header (x-uptimely-service-token and x-uptimely-token
    are accepted as aliases, for OTel distros that send one of those).
  location: header
  header: x-uptimely-ingestion-key
  how_to_obtain: Create a telemetry ingestion key (method not detailed on the page).
- type: oauth2
  name: MCP server
  evidence: It authenticates with OAuth 2.1 (dynamic client registration, PKCE, consent screen in the browser) and covers everything the person
    can do in Uptimely.
  how_to_obtain: User signs in through the browser when the first tool is used; no key is needed.
docs: https://getuptimely.com/docs/api