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

# Whitelist applications closed

> Public whitelist applications are closed.

 Retained for client compatibility. Every decoded submission is rejected with
 HTTP 403 Forbidden / gRPC PERMISSION_DENIED and no applicant data is changed.
 Existing applications and administrative approvals remain available.



## OpenAPI

````yaml /proto-openapi/api/openapi.yaml post /api/v1/whitelist
openapi: 3.0.3
info:
  title: Monaco Protocol API
  description: REST API for the Monaco Protocol hybrid CLOB exchange.
  version: 1.0.0
servers:
  - url: https://staging.apimonaco.xyz
    description: Staging server (Testnet)
security: []
tags:
  - name: AccountsService
  - name: ApplicationsService
  - name: AuthService
  - name: BuildercodeRewardsService
  - name: DelegatedAgentsService
  - name: FaucetService
  - name: FeesService
  - name: HealthService
  - name: ManagedMarketsService
    description: |-
      Wallet-authenticated maker assignments. The signed session must match both
       configured maker user and application. Owner IDs are process fences, never auth.
       Only wallet sessions are supported; delegated-agent sessions receive 403.
  - name: MarginAccountsService
    description: |-
      Current public isolated-margin semantics:
       - a user has one parent margin account per application scope
       - opening orders create or reuse isolated position buckets under that parent
       - parent account creation is handled internally by margin workflows
  - name: MarketService
  - name: OrderbookService
  - name: OrdersService
  - name: PositionsService
    description: |-
      Current public isolated-margin semantics:
       - positions link to a parent margin account and, when applicable, a bucket id
       - opening orders create or reuse isolated position buckets under the parent
       - users can open another isolated position by reusing the parent account with a different market bucket
  - name: PulseService
  - name: SweeperService
  - name: TraderCodeService
  - name: TradesService
  - name: WhitelistService
  - name: WithdrawalsService
paths:
  /api/v1/whitelist:
    post:
      tags:
        - WhitelistService
        - Whitelist
      summary: Whitelist applications closed
      description: |-
        Public whitelist applications are closed.

         Retained for client compatibility. Every decoded submission is rejected with
         HTTP 403 Forbidden / gRPC PERMISSION_DENIED and no applicant data is changed.
         Existing applications and administrative approvals remain available.
      operationId: submit_whitelist
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/SubmitWhitelistRequest'
        required: true
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/SubmitWhitelistResponse'
        '400':
          description: Invalid request parameters
        '403':
          description: >-
            Public whitelist applications are closed. No applicant data is
            changed.
        '500':
          description: Internal server error
      deprecated: true
components:
  schemas:
    SubmitWhitelistRequest:
      required:
        - walletAddress
        - email
      type: object
      properties:
        walletAddress:
          example: '0x742d35Cc6634C0532925a3b8D4060f31E2C3d8B5'
          maxLength: 42
          minLength: 42
          pattern: ^0x[0-9a-fA-F]{40}$
          type: string
          description: Applicant wallet address
        email:
          example: user@example.com
          minLength: 1
          type: string
          description: Applicant email address
          format: email
        twitterUsername:
          example: monaco_user
          maxLength: 15
          minLength: 1
          pattern: ^[A-Za-z0-9_]{1,15}$
          type: string
          description: Applicant Twitter/X username
          nullable: true
        telegramUsername:
          example: monaco_user
          maxLength: 32
          minLength: 5
          pattern: ^[a-zA-Z0-9_]{5,32}$
          type: string
          description: Applicant Telegram username
          nullable: true
      additionalProperties: false
    SubmitWhitelistResponse:
      type: object
      properties:
        message:
          example: >-
            Your whitelist application has been submitted successfully! We'll
            review it and get back to you soon.
          type: string
          description: >-
            Legacy success message; submissions now return HTTP 403 / gRPC
            PERMISSION_DENIED
          nullable: true
        userId:
          example: 123e4567-e89b-12d3-a456-426614174000
          type: string
          description: Legacy created user UUID; retired submissions do not create users
          nullable: true
          format: uuid

````