> ## Documentation Index
> Fetch the complete documentation index at: https://docs.prelude.so/llms.txt
> Use this file to discover all available pages before exploring further.

# Get authorization server metadata

> RFC 8414 authorization-server metadata. Advertises the authorize,
token, registration, and JWKS endpoints an OAuth/MCP client needs.
`registration_endpoint` is present only when Dynamic Client
Registration is enabled, and `client_id_metadata_document_supported`
is `true` only when Client ID Metadata Documents are enabled.




## OpenAPI

````yaml get /.well-known/oauth-authorization-server
openapi: 3.1.1
info:
  title: Prelude Auth Frontend API
  version: 0.0.1
  description: The Prelude Frontend API for Authentication and Session Management
  contact:
    email: support@prelude.so
servers:
  - url: https://{appId}.session.prelude.dev
    description: Production server
    variables:
      appId:
        default: changeme
        description: The appID
security: []
tags:
  - name: Login OTP
    description: Login and step-up via OTP (phone or email)
  - name: Login Email Password
    description: Login via email and password
  - name: Login OAuth
    description: Login via OAuth providers
  - name: Login SAML
    description: Login via SAML 2.0 SSO connections (Okta, Google Workspace)
  - name: Login Finalize
    description: Finalize a login flow and create a session
  - name: Login Migration
    description: Migrate sessions from a legacy authentication system
  - name: Session
    description: Session refresh and revocation
  - name: Session Management
    description: Authenticated session and identifier management
  - name: Step-Up
    description: Step-up authentication flow
  - name: Well-Known
    description: Public key and authorization-server discovery endpoints
  - name: OAuth Server
    description: >-
      OAuth 2.0 authorization-server endpoints that let MCP clients and other
      third-party apps sign your users in
  - name: Password
    description: Password compliancy and change password
  - name: Passkey Login
    description: >-
      Primary-factor (passwordless) sign-in via WebAuthn discoverable
      credentials
  - name: Passkey Management
    description: >-
      Register / list / rename / delete the authenticated user's passkey
      credentials
paths:
  /.well-known/oauth-authorization-server:
    get:
      tags:
        - Well-Known
      summary: Get authorization server metadata
      description: |
        RFC 8414 authorization-server metadata. Advertises the authorize,
        token, registration, and JWKS endpoints an OAuth/MCP client needs.
        `registration_endpoint` is present only when Dynamic Client
        Registration is enabled, and `client_id_metadata_document_supported`
        is `true` only when Client ID Metadata Documents are enabled.
      operationId: getOAuthAuthorizationServerMetadata
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/OAuthAuthorizationServerMetadata'
components:
  schemas:
    OAuthAuthorizationServerMetadata:
      type: object
      description: RFC 8414 authorization-server metadata.
      properties:
        issuer:
          type: string
          examples:
            - https://myapp.session.prelude.dev
        authorization_endpoint:
          type: string
          examples:
            - https://myapp.session.prelude.dev/v1/session/oauth/authorize
        token_endpoint:
          type: string
          examples:
            - https://myapp.session.prelude.dev/v1/session/oauth/token
        registration_endpoint:
          type: string
          description: Present only when Dynamic Client Registration is enabled.
          examples:
            - https://myapp.session.prelude.dev/v1/session/oauth/register
        jwks_uri:
          type: string
          examples:
            - https://myapp.session.prelude.dev/.well-known/jwks.json
        response_types_supported:
          type: array
          items:
            type: string
          examples:
            - - code
        grant_types_supported:
          type: array
          items:
            type: string
          examples:
            - - authorization_code
              - refresh_token
        code_challenge_methods_supported:
          type: array
          items:
            type: string
          examples:
            - - S256
        token_endpoint_auth_methods_supported:
          type: array
          items:
            type: string
          examples:
            - - none
        scopes_supported:
          type: array
          items:
            type: string
        client_id_metadata_document_supported:
          type: boolean
          description: >-
            `true` when Client ID Metadata Documents (CIMD) are enabled for the
            app.
          examples:
            - true
      required:
        - issuer
        - authorization_endpoint
        - token_endpoint
        - jwks_uri
        - response_types_supported
        - grant_types_supported
        - code_challenge_methods_supported
        - token_endpoint_auth_methods_supported

````