> ## 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. # Update sub-account limit > Update sub-account limit. Update an existing limit for a sub-account. Only master accounts can update limits for their sub-accounts. ## OpenAPI ````yaml /proto-openapi/api/openapi.yaml put /api/v1/accounts/sub-accounts/{subAccountId}/limits/{assetId} 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/accounts/sub-accounts/{subAccountId}/limits/{assetId}: put: tags: - AccountsService - Account Limits summary: Update sub-account limit description: |- Update sub-account limit. Update an existing limit for a sub-account. Only master accounts can update limits for their sub-accounts. operationId: update_sub_account_limit parameters: - name: subAccountId in: path required: true schema: type: string default: 2b1a5f9c-0000-4000-8000-000000000005 example: 2b1a5f9c-0000-4000-8000-000000000005 - name: assetId in: path required: true schema: type: string default: 1905d968-cc65-4cc7-b77c-1905d968cc65 example: 1905d968-cc65-4cc7-b77c-1905d968cc65 requestBody: content: application/json: schema: $ref: '#/components/schemas/UpdateLimitRequest' required: true responses: '200': description: OK content: application/json: schema: $ref: '#/components/schemas/UpdateLimitResponse' '400': description: Invalid request '401': description: Authentication required '403': description: Only master accounts can update sub-account limits '404': description: Limit not found '500': description: Internal server error security: - monacoSignature: [] - monacoHttpSignature: [] components: schemas: UpdateLimitRequest: type: object properties: subAccountId: example: 123e4567-e89b-12d3-a456-426614174000 type: string description: Sub-account UUID format: uuid nullable: true assetId: example: 123e4567-e89b-12d3-a456-426614174000 type: string description: Asset UUID format: uuid nullable: true maxAmount: example: '1500.00' minLength: 1 pattern: ^-?[0-9]{1,28}(\.[0-9]{1,18})?$ type: string description: New maximum amount allowed in token units nullable: true dailyLimit: example: '500.00' minLength: 1 pattern: ^-?[0-9]{1,28}(\.[0-9]{1,18})?$ type: string description: New maximum daily spending limit in token units nullable: true isActive: example: true type: boolean description: Whether the limit is active nullable: true additionalProperties: false UpdateLimitResponse: type: object properties: limit: $ref: '#/components/schemas/SubAccountLimit' SubAccountLimit: type: object properties: id: example: 987e6543-e21b-12d3-a456-426614174000 type: string description: Limit UUID format: uuid nullable: true subAccountId: example: 123e4567-e89b-12d3-a456-426614174000 type: string description: Sub-account UUID this limit applies to format: uuid nullable: true token: example: '0x6a86da986797d59a839d136db490292cd560c131' type: string description: Token contract address nullable: true dailyLimit: example: '1000.00' type: string description: Maximum daily spending limit in token units nullable: true usedToday: example: '250.50' type: string description: Amount used today against the limit nullable: true createdAt: example: '2023-11-13T10:30:00Z' type: string description: Limit creation timestamp (ISO 8601) nullable: true updatedAt: example: '2023-11-13T10:30:00Z' type: string description: Last update timestamp (ISO 8601) nullable: true masterAccountId: example: 123e4567-e89b-12d3-a456-426614174001 type: string description: Master account UUID that owns this sub-account format: uuid nullable: true maxAmount: example: '1500.00' type: string description: Maximum amount allowed in token units nullable: true lastResetAt: example: '2023-11-13T00:00:00Z' type: string description: Last reset timestamp for the daily limit (ISO 8601) nullable: true isActive: example: true type: boolean description: Whether the limit is active 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.