Place OCO

Place an OCO (one-cancels-the-other) order strategy.

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.

// Demo environment; for Live use https://live.tradovateapi.com/v1
const URL = 'https://demo.tradovateapi.com/v1'
const oco = {
    accountSpec: yourUserName,
    accountId: yourAccountId,
    action: "Sell",
    symbol: "MESM1",
    orderType: "Limit",
    price: 4200.00,
    orderQty: 1,
    isAutomated: true,
    other: {
        action: "Sell",
        orderType: "Stop",
        stopPrice: 4100.00
    }
}
const result = await fetch(`${URL}/order/placeoco`, {
    method: 'POST',
    headers: {
        'Content-Type': 'application/json',
        'Authorization': `Bearer ${myAccessToken}`
    },
    body: JSON.stringify(oco)
}).then(res => res.json()) // { orderId, ocoId } on success

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

• A risk limit blocks the order (for example, MaxPosLimitReached).
• A contract or price is invalid (InvalidContract, InvalidPrice).
• The trading session is closed (SessionClosed).

Error Messages

See the failureReason enum in the response schema for the complete list of values.