RULE CHANGE
Trading with the API
Competition accounts cannot participate in copy groups; affected saved groups must be disabled.
What this means
Competition accounts cannot lead or follow in copy groups, as prohibited by Competition Rules. POST /v1/copy-trading now rejects enabled groups that include competition accounts. Previously saved groups will not copy lead orders to or from competition accounts and must be disabled using POST /v1/copy-trading/{config_id}/disable.
▸ View exact changes
What the page said before and after
Before Oct 18, 2026
including unrealized P\&L, reaches the profit target, so track
risk.remaining_profit_equity. When it reaches zero, the evaluation passes and
open positions are closed. risk.remaining_profit counts realized profit only
and can stay above zero while open profit already covers the target. Both are
null when the account has no profit target, and remaining_profit_equity is
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.
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 Oct 19, 2026
including unrealized P\&L, reaches the profit target, so track
risk.remaining_profit_equity. When it reaches zero, the evaluation passes and
open positions are closed. risk.remaining_profit counts realized profit only
and can stay above zero while open profit already covers the target. Both are
null when the account has no profit target, and remaining_profit_equity is
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.
including unrealized P\&L, reaches the profit target, so track
risk.remaining_profit_equity. When it reaches zero, the evaluation passes and
open positions are closed. risk.remaining_profit counts realized profit only
and can stay above zero while open profit already covers the target. Both are
null when the account has no profit target, and remaining_profit_equity is
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.