> ## 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. # Follow a lead trader or edit a follow > Follow a lead trader or edit a follow. Without `followId`, creates a follow: `allocation` moves from your margin account into a new copy account for this leader, and from then on the leader's fills are mirrored into it. With `followId`, edits that follow (it must be yours): the leader comes from the follow, so an edit works even after the leader releases their handle, and `leader` may be empty; a `leader` handle that names a different leader is refused. `copyExisting` copies the leader's open positions into the new copy account at creation (see PreviewFollow for what that costs); it applies only to a create, and an edit that sets it is refused. ## OpenAPI ````yaml /proto-openapi/api/openapi.yaml post /api/v1/copy-trading/follows 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: post: tags: - CopyTradingService - Copy Trading summary: Follow a lead trader or edit a follow description: |- Follow a lead trader or edit a follow. Without `followId`, creates a follow: `allocation` moves from your margin account into a new copy account for this leader, and from then on the leader's fills are mirrored into it. With `followId`, edits that follow (it must be yours): the leader comes from the follow, so an edit works even after the leader releases their handle, and `leader` may be empty; a `leader` handle that names a different leader is refused. `copyExisting` copies the leader's open positions into the new copy account at creation (see PreviewFollow for what that costs); it applies only to a create, and an edit that sets it is refused. operationId: upsert_follow requestBody: content: application/json: schema: $ref: '#/components/schemas/UpsertFollowRequest' required: true responses: '200': description: OK content: application/json: schema: $ref: '#/components/schemas/UpsertFollowResponse' '400': description: >- Invalid request, or refused by a follow rule (the message names the rule) '401': description: Authentication required '403': description: Delegated agent or sub-account sessions cannot follow '404': description: Lead trader or follow not found '409': description: Copy trading is not available '500': description: Internal server error '503': description: Matching engine unavailable; retry security: - monacoSignature: [] - monacoHttpSignature: [] components: schemas: UpsertFollowRequest: type: object properties: followId: type: string description: Omit to create a follow; set to edit one of your follows format: uuid nullable: true leader: example: alpha_trader type: string description: >- The leader's custom TraderCode handle; required on a create, optional on an edit (a consistency check when it resolves) nullable: true marginModePolicy: example: FOLLOW type: string description: >- FOLLOW (default: the leader's risk bucket mode per market), CROSS or ISOLATED nullable: true sizingMode: example: PROPORTIONAL type: string description: >- PROPORTIONAL (default: scaled by copy account equity over the leader's equity) or FIXED_MARGIN nullable: true sizingParam: type: string description: >- Margin per leader order in quote units; required for FIXED_MARGIN, omitted otherwise nullable: true leverageMode: example: FOLLOW type: string description: 'FOLLOW (default: the leader''s leverage) or FIXED' nullable: true fixedLeverage: type: string description: Leverage for every copy; required for FIXED, omitted otherwise nullable: true allocation: example: '1000' type: string description: >- Collateral for the copy account, in quote units, at or above the minimum nullable: true slPct: example: '0.25' type: string description: >- Copy stop-loss as a fraction of the allocation in (0, 1]; omitted means none nullable: true copyExisting: type: boolean description: >- On a create, also copy the leader's currently open positions into the new copy account, sized like any mirrored fill (PreviewFollow shows the cost). Default false. Refused on an edit nullable: true markets: allOf: - $ref: '#/components/schemas/CopyMarketFilter' description: Markets to copy; omit to copy every market the leader trades. nullable: true UpsertFollowResponse: type: object properties: followId: type: string description: The follow's id format: uuid nullable: true copyRiskBucketId: type: string description: >- The copy account: the cross risk bucket in your margin account that holds this follow's collateral and positions format: uuid nullable: true created: type: boolean description: True when this call created the follow, false when it edited one nullable: true CopyMarketFilter: type: object properties: tradingPairIds: type: array items: type: string minLength: 1 format: uuid description: Trading pair UUIDs to copy (at most 256); empty means every market. nullable: true description: A follow's market filter. 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 ````