> ## 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. # Close all your copy positions > Close all your copy positions. Closes the copy positions of every live follow of yours, as CloseFollowPositions does for one: one batch per follow, the follows kept, and the same limits (not a flatten guarantee; the follows keep mirroring). A follow whose stop is in progress is listed in `stoppingFollowIds` and left to its stop. A follow whose close could not run is listed in `failedFollows` and the others still close. Never gated by copy trading being switched off or by an operations block; only a delegated agent session is refused. Shares CloseFollowPositions' rate limit. ## OpenAPI ````yaml /proto-openapi/api/openapi.yaml post /api/v1/copy-trading/follows/close-positions 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/copy-trading/follows/close-positions: post: tags: - CopyTradingService - Copy Trading summary: Close all your copy positions description: |- Close all your copy positions. Closes the copy positions of every live follow of yours, as CloseFollowPositions does for one: one batch per follow, the follows kept, and the same limits (not a flatten guarantee; the follows keep mirroring). A follow whose stop is in progress is listed in `stoppingFollowIds` and left to its stop. A follow whose close could not run is listed in `failedFollows` and the others still close. Never gated by copy trading being switched off or by an operations block; only a delegated agent session is refused. Shares CloseFollowPositions' rate limit. operationId: close_all_copy_positions responses: '200': description: OK content: application/json: schema: $ref: '#/components/schemas/CloseAllCopyPositionsResponse' '400': description: The close was refused '401': description: Authentication required '403': description: Delegated agent sessions cannot close copy positions '409': description: Copy trading is not available '429': description: >- Copy position close rate limit exceeded; retry after the interval in details.retryAfter '500': description: Internal server error '503': description: The matching engine is unavailable; retry security: - monacoSignature: [] - monacoHttpSignature: [] components: schemas: CloseAllCopyPositionsResponse: type: object properties: follows: type: array items: $ref: '#/components/schemas/CloseFollowPositionsResponse' description: |- Every live follow whose stop is not in progress and whose close ran, including one with nothing to close (0 orders placed, 0 positions not closed). nullable: true stoppingFollowIds: type: array items: type: string minLength: 1 format: uuid description: >- Follows whose stop is in progress: their stop closes their positions. nullable: true failedFollows: type: array items: $ref: '#/components/schemas/FollowCloseFailure' description: Follows whose close could not run; the other follows still closed. nullable: true CloseFollowPositionsResponse: type: object properties: followId: type: string description: The follow's id format: uuid nullable: true closeOrdersPlaced: example: 2 type: integer description: >- Reduce-only, immediate-or-cancel close orders placed; each may fill in part format: uint32 nullable: true positionsNotClosed: example: 0 type: integer description: >- Copy positions still open after the batch (for example a thin or halted market); 0 when the copy account is flat format: uint32 nullable: true FollowCloseFailure: type: object properties: followId: type: string description: The follow's id format: uuid nullable: true reason: example: The copy positions could not be closed right now; retry shortly type: string description: Why the close could not run, as a fixed sentence; retry the close nullable: true description: A follow whose close could not run. 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.