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

# OAuth 2.0 Authorization Server Metadata (RFC 8414)

> Discovery document advertising the authorize/token endpoints, supported grant types (`authorization_code`, `refresh_token`), PKCE (S256), and supported `token_endpoint_auth_methods` (`none`, `client_secret_post`, `client_secret_basic`). Used by OAuth and MCP clients to auto-configure. Equivalent metadata is also served under `/oauth/.well-known/...` and `/mcp/.well-known/...` variants.



## OpenAPI

````yaml /api-reference/openapi.json get /.well-known/oauth-authorization-server
openapi: 3.1.0
info:
  title: iZap API
  version: v1
  description: Public REST API for the iZap WhatsApp business messaging platform.
  contact:
    name: iZap API Support
    email: suporte@izap.ai
  license:
    name: MIT
    url: https://opensource.org/licenses/MIT
servers:
  - url: https://api.izap.ai
    description: Production
  - url: https://api-staging.izap.ai
    description: Staging
security:
  - bearerAuth: []
tags:
  - name: Auth
    description: Login and token refresh.
  - name: OAuth
    description: OAuth 2.1 / PKCE authorization for third-party and MCP clients.
  - name: Businesses
    description: Business profile, hours, menus, and chatbot configuration.
  - name: Chats
    description: Conversations, messages, and template sends.
  - name: Scheduling
    description: Customers, services, providers, and bookings (Trinks-backed).
  - name: WhatsApp Templates
    description: Manage and sync WhatsApp message templates.
  - name: Transmissions
    description: Bulk WhatsApp template broadcasts.
  - name: Me
    description: The authenticated user's own profile and active business.
paths:
  /.well-known/oauth-authorization-server:
    get:
      tags:
        - OAuth
      summary: OAuth 2.0 Authorization Server Metadata (RFC 8414)
      description: >-
        Discovery document advertising the authorize/token endpoints, supported
        grant types (`authorization_code`, `refresh_token`), PKCE (S256), and
        supported `token_endpoint_auth_methods` (`none`, `client_secret_post`,
        `client_secret_basic`). Used by OAuth and MCP clients to auto-configure.
        Equivalent metadata is also served under `/oauth/.well-known/...` and
        `/mcp/.well-known/...` variants.
      operationId: getOAuthAuthorizationServerMetadata
      responses:
        '200':
          description: Authorization server metadata.
          content:
            application/json:
              schema:
                type: object
                additionalProperties: true
              example:
                issuer: https://api.izap.ai
                authorization_endpoint: https://api.izap.ai/oauth/authorize
                token_endpoint: https://api.izap.ai/oauth/token
                registration_endpoint: https://api.izap.ai/oauth/register
                grant_types_supported:
                  - authorization_code
                  - refresh_token
                code_challenge_methods_supported:
                  - S256
                token_endpoint_auth_methods_supported:
                  - none
                  - client_secret_post
                  - client_secret_basic
        '401':
          description: Not applicable (public endpoint); included for schema consistency.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
              example:
                detail: Not authenticated
      security: []
components:
  schemas:
    Error:
      type: object
      properties:
        detail:
          type: string
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: >-
        JWT access token obtained from POST /api/v1/auth/jwt/login, the OAuth
        token endpoint, or a business-scoped API token. Some
        Business/Chat/Template/Scheduling endpoints alternatively accept HTTP
        Basic credentials scoped to the business slug.

````