Dream Sports · Authentication Profile

Dream Sports Authentication

Authentication

Dream Sports secures its APIs with apiKey, http, and openIdConnect across 6 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode flow(s).

Companysports-technologyfantasy-sportsopen-sourcedeveloper-toolsplatform-engineeringauthenticationopenid-connectoauth2mobilereact-nativedevopsobservabilitytest-managementota-updatesfeature-flagsindiamcpagent-native
Methods: apiKey, http, openIdConnect Schemes: 6 OAuth flows: authorizationCode API key in: cookie, header

Security Schemes

Login with Dream11 openIdConnect
· flows: authorizationCode
Guardian Authorization header http
scheme: bearer
Odin platform bearer token http
scheme: bearer
cookieAuth apiKey
· in: cookie (user_session)
bearerAuth http
scheme: bearer
TenantIdHeader apiKey
· in: header (TENANT-ID)

Source

Authentication Profile

Raw ↑
generated: '2026-08-04'
method: searched
source: openapi/dream-sports-checkmate-openapi.yml, openapi/dream-sports-delivr-ota-openapi.yml,
  openapi/dream-sports-dota-openapi.yml, openapi/dream-sports-raven-journey-openapi.yml
docs: https://guardianhq.io/docs/
upgrade_note: >-
  The mechanical derivation found only the three securitySchemes below, because the two largest
  Dream Sports auth surfaces declare none in-spec: the Guardian OpenAPI documents Authorization as a
  plain header parameter rather than a securityScheme, and the live "Login with Dream11" OIDC service
  is not described by any OpenAPI at all. Both are added here from the provider's own published
  material — the Guardian docs and the live discovery document — which is what raises this file from
  derived to searched.
summary:
  types:
  - apiKey
  - http
  - openIdConnect
  api_key_in:
  - cookie
  - header
  oauth2_flows:
  - authorizationCode
schemes:
- name: Login with Dream11
  type: openIdConnect
  openIdConnectUrl: https://auth.dream11.com/.well-known/openid-configuration
  issuer: https://auth.dream11.com
  flows:
  - flow: authorizationCode
    authorizationUrl: https://auth.dream11.com/authorize
    tokenUrl: https://auth.dream11.com/token
    refresh: supported (refresh_token grant)
    revocationUrl: https://auth.dream11.com/revokeToken
  jwks_uri: https://auth.dream11.com/certs
  id_token_alg: RS256
  scopes: 7
  description: >-
    Dream11's production identity service — a single-tap, OTP-less login/registration mechanism that
    lets a third-party app authenticate a user as their Dream11 account, with an in-built consent
    flow controlling which profile claims are shared. Scopes and claims in
    scopes/dream-sports-scopes.yml.
  sources:
  - well-known/dream-sports-openid-configuration.json
  method: probed
- name: Guardian Authorization header
  type: http
  scheme: bearer
  description: >-
    Guardian's own endpoints take Authorization as a declared header parameter rather than an OpenAPI
    securityScheme, so the derivation could not see it. The Guardian docs describe the full method
    set: passwordless (OTP over SMS/email), username/password, social login (Google, Facebook),
    generic OIDC provider connect, biometric challenge/complete, guest login, and session management
    with refresh tokens and admin logout. Guardian can also act as an identity provider itself
    (authorize / token / userinfo / certs / revoke) with PKCE.
  tenancy_header: TENANT-ID
  sources:
  - openapi/dream-sports-guardian-openapi.yml
  - https://guardianhq.io/docs/
  method: searched
- name: Odin platform bearer token
  type: http
  scheme: bearer
  description: >-
    odin-deployer, odin-scout and user-auth all take the same Authorization bearer value, passed as a
    REST header and as gRPC metadata. Org-scoped routes additionally need X-Org-Id, which odin-mcp
    fills from a tool argument or from the JWT orgid claim.
  sources:
  - https://github.com/dream-horizon-org/odin-mcp
  method: searched
- name: cookieAuth
  type: apiKey
  in: cookie
  parameter: user_session
  description: |-
    Session cookie from Google OAuth authentication.

    **How to get:**
    1. Navigate to /login
    2. Authenticate with Google
    3. Cookie is automatically set

    **Usage:**
    - Browsers automatically include this cookie
    - cURL: Use `-b cookies.txt` or `-H "Cookie: user_session=value"`
  sources:
  - openapi/dream-sports-checkmate-openapi.yml
- name: bearerAuth
  type: http
  scheme: bearer
  bearerFormat: Token
  description: |-
    API token authentication for programmatic access.

    **How to get:**
    1. Login via web interface
    2. Call POST /api/v1/token/generate with your userId
    3. Copy the returned token

    **Usage:**
    - Include in Authorization header: `Bearer your_token_here`
    - Example: `Authorization: Bearer abc123xyz`
  sources:
  - openapi/dream-sports-checkmate-openapi.yml
  - openapi/dream-sports-delivr-ota-openapi.yml
  - openapi/dream-sports-dota-openapi.yml
- name: TenantIdHeader
  type: apiKey
  in: header
  parameter: TENANT-ID
  sources:
  - openapi/dream-sports-raven-journey-openapi.yml