RULE CHANGE
Trading with the API
Copy trading now has a 20-group maximum limit that includes disabled and stopped groups.
What this means
Copy groups are now limited to at most 20 total, with disabled and stopped groups counting toward this limit; exceeding it returns a 422 error with copy_configuration_rejected; users can delete stopped groups in the same request using deleted_config_ids to make room. Previously, there was no documented maximum limit on copy groups.
▸ View exact changes
What the page said before and after
Before Nov 12, 2026
also null when marks are incomplete.
Copy groups and scheduled execution
Before submitting a lead order through the API, ensure the credential covers
the lead and every follower. The same boundary applies to modifications,
cancellations, and protective exits. A scope failure rejects the complete
native order operation, preserving the copy group's behavior rather than
silently dropping a follower. See Authentication.
Competition accounts cannot lead or follow in a copy group, because the
Competition Rules prohibit copying trades into or out of them.
POST /v1/copy-trading rejects an enabled group that includes one. A group
saved before this rule does not copy lead orders to or from a competition
account; disable it with POST /v1/copy-trading/{config_id}/disable.
Accepted TWAP/VWAP and scaled orders retain the environment and account scope
that authorized them. Revoking the key blocks new requests but does not revoke
that accepted schedule. Each later slice or rung checks the current copy group
against its retained scope. If the group now includes an inaccessible account,
TWAP/VWAP stops with completion_reason: "api_account_scope_changed"; scaled
orders reject the remaining unplaced rungs with that reject_reason. Previously
accepted child orders are not canceled, and filled positions are not closed.
Older API schedules created before scope was retained can recover their
boundary while the original key still exists. If that key has been deleted,
only the schedule's own account can be established: an enabled copy group
causes future slices or rungs to stop rather than assume broader access. Finish
or recreate an older copied schedule before deleting its original key.
After Nov 18, 2026
also null when marks are incomplete.
Copy groups and scheduled execution
Before submitting a lead order through the API, ensure the credential covers
the lead and every follower. The same boundary applies to modifications,
cancellations, and protective exits. A scope failure rejects the complete
native order operation, preserving the copy group's behavior rather than
silently dropping a follower. See Authentication.
Competition accounts cannot lead or follow in a copy group, because the
Competition Rules prohibit copying trades into or out of them.
POST /v1/copy-trading rejects an enabled group that includes one. A group
saved before this rule does not copy lead orders to or from a competition
account; disable it with POST /v1/copy-trading/{config_id}/disable.
+ A user can keep at most 20 copy groups, and disabled and stopped groups count
+ toward that limit. POST /v1/copy-trading returns 422
+ copy_configuration_rejected for a save that would exceed it. To make room in
+ the same request, list stopped groups in deleted_config_ids.
Accepted TWAP/VWAP and scaled orders retain the environment and account scope
that authorized them. Revoking the key blocks new requests but does not revoke
that accepted schedule. Each later slice or rung checks the current copy group
against its retained scope. If the group now includes an inaccessible account,
TWAP/VWAP stops with completion_reason: "api_account_scope_changed"; scaled
orders reject the remaining unplaced rungs with that reject_reason. Previously
accepted child orders are not canceled, and filled positions are not closed.
Older API schedules created before scope was retained can recover their
boundary while the original key still exists. If that key has been deleted,
only the schedule's own account can be established: an enabled copy group
causes future slices or rungs to stop rather than assume broader access. Finish
or recreate an older copied schedule before deleting its original key.
also null when marks are incomplete.
Copy groups and scheduled execution
Before submitting a lead order through the API, ensure the credential covers
the lead and every follower. The same boundary applies to modifications,
cancellations, and protective exits. A scope failure rejects the complete
native order operation, preserving the copy group's behavior rather than
silently dropping a follower. See Authentication.
Competition accounts cannot lead or follow in a copy group, because the
Competition Rules prohibit copying trades into or out of them.
POST /v1/copy-trading rejects an enabled group that includes one. A group
saved before this rule does not copy lead orders to or from a competition
account; disable it with POST /v1/copy-trading/{config_id}/disable.
+ A user can keep at most 20 copy groups, and disabled and stopped groups count
+ toward that limit. POST /v1/copy-trading returns 422
+ copy_configuration_rejected for a save that would exceed it. To make room in
+ the same request, list stopped groups in deleted_config_ids.
Accepted TWAP/VWAP and scaled orders retain the environment and account scope
that authorized them. Revoking the key blocks new requests but does not revoke
that accepted schedule. Each later slice or rung checks the current copy group
against its retained scope. If the group now includes an inaccessible account,
TWAP/VWAP stops with completion_reason: "api_account_scope_changed"; scaled
orders reject the remaining unplaced rungs with that reject_reason. Previously
accepted child orders are not canceled, and filled positions are not closed.
Older API schedules created before scope was retained can recover their
boundary while the original key still exists. If that key has been deleted,
only the schedule's own account can be established: an enabled copy group
causes future slices or rungs to stop rather than assume broader access. Finish
or recreate an older copied schedule before deleting its original key.