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

# Get authorization details for consent screen

> ⚠️ SECURITY: Returns OAuth application details and requested scopes for displaying a consent screen. User must be authenticated. Validates client_id, redirect_uri, and scopes.



## OpenAPI

````yaml https://api.timbrix.mx/api/openapi.json get /oauth/authorize/details
openapi: 3.0.0
info:
  title: Timbrix API
  description: >-
    API de facturación electrónica CFDI 4.0 para México, con servidor OAuth2
    para gestionar organizaciones, miembros y webhooks. Compatible con agentes
    de IA — ver la extensión `x-ai-agent-friendly` en la raíz de esta spec.


    REST API with OAuth2 server for managing organizations, members, and
    webhooks.
  version: '1.0'
  contact: {}
servers: []
security: []
tags:
  - name: organizations
    description: Organization management endpoints
  - name: oauth
    description: OAuth2 authentication and authorization
  - name: webhooks
    description: Webhook configuration and delivery
  - name: users
    description: User information endpoints
  - name: api-keys
    description: API Keys management and validation
paths:
  /oauth/authorize/details:
    get:
      tags:
        - oauth
      summary: Get authorization details for consent screen
      description: >-
        ⚠️ SECURITY: Returns OAuth application details and requested scopes for
        displaying a consent screen. User must be authenticated. Validates
        client_id, redirect_uri, and scopes.
      operationId: OAuthController_getAuthorizationDetails
      parameters:
        - name: client_id
          required: true
          in: query
          description: OAuth application client ID
          schema:
            example: app_abc123...
            type: string
        - name: redirect_uri
          required: true
          in: query
          description: Redirect URI for the authorization flow
          schema:
            example: https://example.com/oauth/callback
            type: string
        - name: scope
          required: true
          in: query
          description: Requested OAuth scopes (comma-separated)
          schema:
            example: read:user,read:organization
            type: string
        - name: state
          required: true
          in: query
          description: State parameter for CSRF protection
          schema:
            example: random_state_abc123
            type: string
        - name: response_type
          required: false
          in: query
          description: Response type (should be 'code')
          schema:
            example: code
            type: string
      responses:
        '200':
          description: >-
            Authorization details retrieved successfully. Returns application
            info and requested scopes with descriptions.
        '401':
          description: Authentication required or invalid client_id/redirect_uri/scopes.
      security:
        - bearer: []
components:
  securitySchemes:
    bearer:
      scheme: bearer
      bearerFormat: JWT
      type: http

````