Replay Authentication

generated: '2026-07-20'
method: searched
source: https://docs.replay.io/reference/integrations/replay-apis/graphql-api
docs: https://docs.replay.io/reference/replay-cli/commands
summary:
  types: [apiKey, oauth2, openIdConnect]
  api_key_in: [header]
  oauth2_flows: [authorizationCode, deviceCode]
schemes:
  - name: ReplayApiKey
    type: http
    scheme: bearer
    description: >
      Programmatic access to the GraphQL API (https://api.replay.io/v1/graphql) and the Replay
      MCP server (https://dispatch.replay.io/nut/mcp) uses a Replay API key presented as a bearer
      token: `Authorization: Bearer ${REPLAY_API_KEY}`. Keys are created under Settings > API Keys
      at https://app.replay.io/team/settings and are commonly set as the REPLAY_API_KEY env var for
      the CLI and test integrations.
    docs: https://docs.replay.io/reference/integrations/replay-apis/graphql-api
    applies_to: [GraphQL API, MCP server, CLI, Playwright/Cypress reporters, source-map upload]
  - name: Auth0OIDC
    type: openIdConnect
    openIdConnectUrl: https://app.replay.io/.well-known/openid-configuration
    issuer: https://webreplay.us.auth0.com/
    description: >
      Interactive login to the Replay web app is delegated to an Auth0 tenant
      (webreplay.us.auth0.com). Discovery documents are served from app.replay.io and expose the
      authorization, token, device-authorization, userinfo, and revocation endpoints. `replayio
      login` uses this flow via the browser.
    source: well-known/replay-openid-configuration.json
    flows: [authorizationCode, deviceCode]
notes: >
  No OpenAPI is published (the primary programmatic surface is GraphQL), so this profile is
  searched from the docs and the live OIDC discovery documents rather than derived from a spec.