Skip to main content
Open Copy Trading settings

​
Group controls

Each group contains:
  • one Lead Account that sends eligible trading instructions;
  • one or more Follower Accounts;
  • a multiplier from 0.1× to 2× for each follower;
  • an enabled, stopping, or stopped lifecycle.
An account can participate in only one enabled group. Groups remain the same when you switch the active account elsewhere in the app.

​
Lead Account

Choose the account that should drive the group. Changing the lead of an existing group requires disabling that group first. If the lead is no longer active or available, disable the group before editing its membership.

​
Follower Accounts and Multipliers

Add active accounts you own. A funded account cannot follow an evaluation lead. The multiplier adjusts the follower’s balance-normalized opening quantity:
  • below 1× uses less relative size;
  • 1× uses the same relative size after starting-balance normalization;
  • above 1× uses more relative size, subject to the follower’s own limits.
Every follower keeps independent collateral, challenge-rule, position, and market checks. One follower can reject an instruction without blocking the lead. API credentials must cover the lead and every follower in the same live or sandbox environment. If a group includes an account outside that boundary, the API rejects the native lead operation before copying any orders. Use a credential covering the complete group or manage the instruction on the website. See Authentication for copied-order changes and scheduled execution boundaries.

​
Disable and remove

Disable the group before removing it or selecting another lead. During stop cleanup, follower orders are canceled and positions are closed. The affected followers remain locked against manual trading until cleanup finishes. If the lead passes, fails, or is closed, the group stops automatically. The stopped record identifies why and can be removed after cleanup completes. Read the Copy Trading Guide for sizing examples, stage compatibility, and the full lifecycle.

​
Manage copy groups through the API

API keys with read scope can inspect GET /v1/copy-trading. A group is returned only when the credential can access its lead and every follower in the same live or sandbox environment. A restricted key can therefore see fewer groups than the website. Accessible groups with archived members remain listed so they can be disabled or deleted. Keys with trade scope can use these operations: Saving applies the same ownership, account status, stage, sizing, disjoint-group, and cleanup rules as the website. Every existing and new member must be accessible to the credential. Groups omitted from a save are preserved; only IDs in deleted_config_ids are deleted. A group must be disabled before it can be deleted or its lead changed. Pending stop cleanup must finish first.
Include config_id when updating an existing group. The save response returns config_ids in submitted-group order, including newly created IDs. A multiplier of 10000 uses proportional sizing after the follower-to-lead starting balance ratio. There can be at most 20 groups and 20 followers per group; multipliers range from 1000 to 20000 basis points. Creating a group is not idempotent. If the response is lost, list the groups and reconcile the intended configuration before retrying. Disabling stops new copying and schedules outstanding copied-order cleanup; it does not close existing filled positions. Automatic stops caused by a terminal lead follow the normal follower close-out process. Before acknowledging a stop, read GET /v1/accounts/{account_id}/trading-policy. Its account-backed copy_stop contains stopped_at, completed_at, acknowledged_at, and reason, even when the original group has been deleted or is hidden from this credential. When completed_at is present, acknowledge with the exact copy_stop.stopped_at Unix-millisecond timestamp as the request’s stopped_at. An outdated timestamp or unfinished cleanup is a no-op.