Place OSO
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 OSO strategy places a primary order that, once filled, automatically submits one or two bracket orders — for example, an entry order that sends a take-profit when it fills. Provide the primary order’s fields plus bracket1 (required) and, optionally, bracket2. If you specify both brackets, they’re linked to each other as an OCO, so filling one cancels the other. On success, the response includes the primary order’s orderId.
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.