> ## 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. # List my Mainnet invite codes > List the authenticated wallet's invite allowance and the codes it minted. Read-only: never mints or consumes an allowance slot, so a client can poll it to show progress and to recover a code whose mint response was lost. ## OpenAPI ````yaml /proto-openapi/api/openapi.yaml get /api/v1/invite-codes 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: CopyTradingService - 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/invite-codes: get: tags: - AuthService - Auth summary: List my Mainnet invite codes description: >- List the authenticated wallet's invite allowance and the codes it minted. Read-only: never mints or consumes an allowance slot, so a client can poll it to show progress and to recover a code whose mint response was lost. operationId: list_invite_codes responses: '200': description: OK content: application/json: schema: $ref: '#/components/schemas/ListInviteCodesResponse' '401': description: Authentication required '403': description: >- Delegated-agent sessions cannot read the owner's invite codes; deactivated signing accounts receive ACCOUNT_DEACTIVATED '429': description: Request rate limit exceeded '500': description: Internal server error '503': description: Mainnet invite access is temporarily unavailable security: - monacoSignature: [] - monacoHttpSignature: [] components: schemas: ListInviteCodesResponse: type: object properties: mainnetVolumeUsd: example: '250000.00' type: string description: >- Executed Mainnet USDC quote notional since the configured production launch, counting maker and taker wallets at 1 USDC = 1 USD. Zero until volume rewards and the launch timestamp are configured. nullable: true eligibleMilestones: example: 1 type: integer description: Number of completed Mainnet volume milestones of 250,000 USDC each. format: int32 nullable: true totalAllowance: example: 2 type: integer description: >- One initial code plus the number of completed Mainnet volume milestones of 250,000 USDC each; zero without active Mainnet access. format: int32 nullable: true availableCodes: example: 1 type: integer description: Allowance slots not yet minted. Revoked slots remain consumed. format: int32 nullable: true codes: type: array items: $ref: '#/components/schemas/InviteCode' description: Codes this wallet minted or was issued, newest first. nullable: true InviteCode: type: object properties: codeId: type: string description: Identifier of the code. format: uuid nullable: true milestone: example: 0 type: integer description: >- Allowance slot: 0 for the initial code, N for the Nth 250,000 USDC milestone. format: int32 nullable: true status: example: issued type: string description: 'Lifecycle status: issued, redeemed or revoked.' nullable: true code: type: string description: >- The 10-character case-sensitive bearer code, present only while it is issued and unredeemed. Store securely; never log it. nullable: true createdAt: type: string description: RFC 3339 time the code was created. format: date-time nullable: true redeemedAt: type: string description: RFC 3339 time the code was redeemed; absent until then. format: date-time nullable: true securitySchemes: monacoSignature: type: apiKey description: >- Ed25519 session-key request signing. Every authenticated request carries three headers: `X-Monaco-PublicKey` (64-char lowercase-hex session public key), `X-Monaco-Timestamp` (Unix milliseconds, within 30s of server time), and `X-Monaco-Signature` (hex ed25519 signature). The signature is over `METHOD\npath?query\ntimestamp_ms\nSHA256_hex(body)`, where the body hash is the SHA-256 of the empty byte string when there is no body. Obtain the session keypair from `POST /api/v1/auth/challenge` followed by `POST /api/v1/auth/verify`. name: X-Monaco-Signature in: header monacoHttpSignature: type: apiKey description: >- RFC 9421 Ed25519 session-key request signatures. Send Signature-Input, Signature, and Content-Digest together; never combine them with X-Monaco-* credentials. The monaco signature covers @method, @path, @query, and content-digest in that order, with created (Unix seconds within 30s of server time), keyid (registered lowercase-hex session public key), and alg=ed25519 parameters. Content-Digest uses RFC 9530 sha-256 over the exact body bytes, including the empty body. Query coverage retains ordering and percent encoding. Timestamp freshness does not reject repeated identical requests; use endpoint idempotency where supported. Existing legacy signing remains supported during server-first migration; SDK RFC 9421 signing is opt-in. See https://docs.0xmonaco.com/reference/http-message-signatures for the complete profile and trust model. name: Signature in: header ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.