Place OCO
Authentication
Bearer authentication of the form Bearer <token>, where token is your auth token.
Bearer authentication of the form Bearer <token>, where token is your auth token.
Available to: All authenticated users
Environments: Demo, Live
Rate Limit: 1,500 requests per hour, 1-second back-off, counts all requests
An OCO strategy links two orders so that when one fills, the other is automatically cancelled — commonly used to pair a take-profit with a stop-loss. Provide the primary order’s fields (account, action, symbol, orderQty, orderType, and the price fields its type requires), plus an other object describing the linked order. The other order’s own action and orderType determine which price fields it needs. On success, the response includes both an orderId and an ocoId.
Set isAutomated to true for any order placed by code or an automated process, and false only for an order a human places directly. Misreporting this can violate exchange policies.
As with any order, acceptance is subject to market, exchange, and risk-management rules. When rejected, the response carries a failureReason and failureText.
Common Failure Scenarios
MaxPosLimitReached).InvalidContract, InvalidPrice).SessionClosed).Error Messages
See the failureReason enum in the response schema for the complete list of values.