> ## 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. # Set your self-trade-prevention default > Set your self-trade-prevention default. Set the authenticated wallet's self-trade-prevention default to one of `CANCEL_MAKER`, `CANCEL_TAKER`, `CANCEL_BOTH`, or `SKIP` (input is case-insensitive; responses always carry these spellings). The default is wallet-scoped — it covers every application and account sharing the wallet address — and a per-order mode always overrides it. The write is sequenced through the matching engine; on success the next order from the wallet family already resolves the new mode. Delegated-agent sessions cannot change it. It spends the per-account settings-write rate limit (about one write per second, burst 10) that the copy trading lead trader and follow writes share. ## OpenAPI ````yaml /proto-openapi/api/openapi.yaml put /api/v1/accounts/self-trade-prevention 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/self-trade-prevention: put: tags: - AccountsService - Accounts summary: Set your self-trade-prevention default description: |- Set your self-trade-prevention default. Set the authenticated wallet's self-trade-prevention default to one of `CANCEL_MAKER`, `CANCEL_TAKER`, `CANCEL_BOTH`, or `SKIP` (input is case-insensitive; responses always carry these spellings). The default is wallet-scoped — it covers every application and account sharing the wallet address — and a per-order mode always overrides it. The write is sequenced through the matching engine; on success the next order from the wallet family already resolves the new mode. Delegated-agent sessions cannot change it. It spends the per-account settings-write rate limit (about one write per second, burst 10) that the copy trading lead trader and follow writes share. operationId: set_self_trade_prevention_default requestBody: content: application/json: schema: $ref: '#/components/schemas/SetSelfTradePreventionDefaultRequest' required: true responses: '200': description: OK content: application/json: schema: $ref: '#/components/schemas/SelfTradePreventionDefaultResponse' '400': description: Unknown mode '401': description: Authentication required '403': description: Delegated-agent sessions cannot change account settings '429': description: >- Settings write rate limit exceeded — the lead trader profile, follow create/edit and self-trade-prevention default share a per-account budget (and the budget the account family shares); retry after the interval in details.retryAfter '500': description: Internal server error security: - monacoSignature: [] - monacoHttpSignature: [] components: schemas: SetSelfTradePreventionDefaultRequest: required: - mode type: object properties: mode: example: SKIP type: string description: >- The self-trade-prevention mode applied when an order from this wallet would match the wallet family's own resting order and the order names no override: `CANCEL_MAKER` (cancel the resting order — the platform default), `CANCEL_TAKER` (cancel the incoming order), `CANCEL_BOTH`, or `SKIP` (trade around own orders). Input is case-insensitive. additionalProperties: false SelfTradePreventionDefaultResponse: type: object properties: mode: example: CANCEL_MAKER type: string description: >- The wallet's effective self-trade-prevention default: `CANCEL_MAKER`, `CANCEL_TAKER`, `CANCEL_BOTH`, or `SKIP`. nullable: true isCustom: example: false type: boolean description: >- True when this wallet has explicitly set a default; false when the platform default (`CANCEL_MAKER`) is in effect. 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.