# cTrader ProtoOANewOrderReq Independent and unofficial. Not affiliated with or endorsed by any broker or platform named here. Educational only: nothing here is advice, and nothing here recommends a broker or a trade. This is the markdown version of https://openbrokerapi.com/platforms/ctrader/messages/protooaneworderreq, written from the same records as that page. Risk warning: CFDs and spread bets are complex instruments and come with a high risk of losing money rapidly due to leverage. You can lose money on these products, and each provider publishes its own loss figure under FCA rules. You should consider whether you understand how they work and whether you can afford to take the high risk of losing your money. Automated and API trading can amplify losses through bugs, connectivity failures and runaway orders. Sends a new order. The definition allows it only where the access token has trade permission for the account. - Message: `ProtoOANewOrderReq` - Interface: cTrader Open API - Group: Orders and positions - Status: verified. Source: [help.ctrader.com](https://help.ctrader.com/open-api/messages/#protooaneworderreq), checked 2026-10-12. - The definition file it was checked against: https://github.com/spotware/openapi-proto-messages/blob/main/OpenApiMessages.proto This is a message of the cTrader Open API, not an HTTP endpoint. It has no method and no path: it is sent over an open TCP or WebSocket connection, as Protocol Buffers or as JSON. It is in no OpenAPI file on this site and the request builder does not list it. Note: This message places a real order when the connection is to the live host. The server answers an accepted or filled order with ProtoOAExecutionEvent, and the definition describes ProtoOAOrderErrorEvent as what is sent when an order request meets an error. No JSON sample is given here. A required field of this message is an enumeration, and Spotware's page on sending and receiving JSON does not say how an enumeration value is written in JSON. ## The message - Name: `ProtoOANewOrderReq` - Direction: Request, sent by the client - Payload type: `PROTO_OA_NEW_ORDER_REQ`, number `2106`. This number is what identifies the message on the wire. - Answered by: [ProtoOAExecutionEvent](https://openbrokerapi.com/platforms/ctrader/messages/protooaexecutionevent) ## Fields - `payloadType` (type ProtoOAPayloadType, optional): Identifies the message. Its default in the definition is PROTO_OA_NEW_ORDER_REQ, which is number 2106. - `ctidTraderAccountId` (type int64, required): The account the message is about, by its cTrader account id. Responses and events carry the same id, which is how a program holding several accounts on one connection tells them apart. - `symbolId` (type int64, required): The symbol, by its id on the cTrader platform. Ids come from the symbol list. - `orderType` (type ProtoOAOrderType, required): The kind of order, as a value of ProtoOAOrderType: MARKET, LIMIT, STOP, MARKET_RANGE or STOP_LIMIT. - `tradeSide` (type ProtoOATradeSide, required): The direction, as a value of ProtoOATradeSide: BUY or SELL. - `volume` (type int64, required): The size. In hundredths of a unit, so 1000 means 10.00 units. - `limitPrice` (type double, optional): The limit price. The definition says it can be given for a LIMIT order only. - `stopPrice` (type double, optional): The stop price. The definition says it can be given for STOP and STOP_LIMIT orders only. - `timeInForce` (type ProtoOATimeInForce, optional): How long the order stands or how it must fill, as a value of ProtoOATimeInForce: GOOD_TILL_DATE, GOOD_TILL_CANCEL, IMMEDIATE_OR_CANCEL, FILL_OR_KILL or MARKET_ON_OPEN. Default: GOOD_TILL_CANCEL. - `expirationTimestamp` (type int64, optional): When the order expires, as Unix time in milliseconds. To be set for good till date orders. - `stopLoss` (type double, optional): The stop loss as an absolute price, for example 1.23456. The definition says it is not supported for market orders. - `takeProfit` (type double, optional): The take profit as an absolute price, for example 1.23456. The definition says it is not supported for market orders. - `comment` (type string, optional): A comment of your own. At most 512 characters. - `baseSlippagePrice` (type double, optional): The price that the slippage of a MARKET_RANGE order is measured from. - `slippageInPoints` (type int32, optional): The slippage distance for MARKET_RANGE and STOP_LIMIT orders. - `label` (type string, optional): A label of your own. At most 100 characters. - `positionId` (type int64, optional): An existing position, where the order is meant to change it. - `clientOrderId` (type string, optional): An id of your own for the order, which the definition likens to ClOrdID in FIX. At most 50 characters. - `relativeStopLoss` (type int64, optional): The stop loss as a distance from the entry price instead of an absolute price, in 1/100000 of a price unit. For a buy it is taken off the entry price, for a sell it is added. - `relativeTakeProfit` (type int64, optional): The take profit as a distance from the entry price instead of an absolute price, in 1/100000 of a price unit. For a buy it is added to the entry price, for a sell it is taken off. - `guaranteedStopLoss` (type bool, optional): True makes the stop loss a guaranteed one. The definition says it has to be true for limited risk accounts. - `trailingStopLoss` (type bool, optional): True makes the stop loss a trailing one. - `stopTriggerMethod` (type ProtoOAOrderTriggerMethod, optional): What triggers a STOP or STOP_LIMIT order, as a value of ProtoOAOrderTriggerMethod. Default: TRADE. ## Limits that apply at cTrader Open API - Requests a second, not historical data: 50 requests per second - Scope: Per connection, requests that are not for historical data - Status: verified. Source: [help.ctrader.com](https://help.ctrader.com/open-api/), checked 2026-10-12. - Note: Historical data requests have their own lower limit, held in a separate record. - Requests a second, historical data: 5 requests per second - Scope: Per connection, historical data requests only - Status: verified. Source: [help.ctrader.com](https://help.ctrader.com/open-api/), checked 2026-10-12. ## Related cTrader messages: Orders and positions - [ProtoOAAmendOrderReq](https://openbrokerapi.com/platforms/ctrader/messages/protooaamendorderreq): Changes a pending order: its size, its prices, its expiry or its stop loss and take profit. The definition allows it only where the access token has trade permission for the account. - [ProtoOAAmendPositionSLTPReq](https://openbrokerapi.com/platforms/ctrader/messages/protooaamendpositionsltpreq): Changes the stop loss and take profit of an open position. The definition allows it only where the access token has trade permission for the account. - [ProtoOACancelOrderReq](https://openbrokerapi.com/platforms/ctrader/messages/protooacancelorderreq): Cancels a pending order. The definition allows it only where the access token has trade permission for the account. - [ProtoOAClosePositionReq](https://openbrokerapi.com/platforms/ctrader/messages/protooaclosepositionreq): Closes an open position, in full or in part. The definition allows it only where the access token has trade permission for the account. - [ProtoOADealListReq](https://openbrokerapi.com/platforms/ctrader/messages/protooadeallistreq): Asks for the account's deals in a period of time. A deal is one execution, so this is the trade history. - [ProtoOADealListRes](https://openbrokerapi.com/platforms/ctrader/messages/protooadeallistres): Returns the deals in the period, one page at a time. - [ProtoOAExecutionEvent](https://openbrokerapi.com/platforms/ctrader/messages/protooaexecutionevent): Sent when the server accepts or executes an order. It is the answer to the new order, cancel, amend and close requests, and it is also sent when a deposit or withdrawal takes place. - [ProtoOAExpectedMarginReq](https://openbrokerapi.com/platforms/ctrader/messages/protooaexpectedmarginreq): Asks for an estimate of the margin a trade would need under the account's leverage profile, which the definition says can be done before a new order is sent. - [ProtoOAExpectedMarginRes](https://openbrokerapi.com/platforms/ctrader/messages/protooaexpectedmarginres): Returns the margin estimate for buying and for selling, for each size that was asked about. - [ProtoOAOrderErrorEvent](https://openbrokerapi.com/platforms/ctrader/messages/protooaordererrorevent): Sent when an order request meets an error. It names the error and, where they apply, the order and the position. - [ProtoOAOrderListReq](https://openbrokerapi.com/platforms/ctrader/messages/protooaorderlistreq): Asks for the account's orders in a period of time. - [ProtoOAOrderListRes](https://openbrokerapi.com/platforms/ctrader/messages/protooaorderlistres): Returns the orders in the period, one page at a time. ## More on cTrader - [All cTrader messages](https://openbrokerapi.com/platforms/ctrader/messages): 49 documented here, grouped by what they do. - [Place an order: the call at each API](https://openbrokerapi.com/endpoints/place-order): The same job at every broker and platform API recorded here, HTTP or not. - [cTrader API quickstart](https://openbrokerapi.com/platforms/ctrader/quickstart) - [All cTrader error codes](https://openbrokerapi.com/errors/ctrader) - [cTrader API page](https://openbrokerapi.com/platforms/ctrader): The full record: access, authentication, limits and the source for each. ## Licence and how to cite The records behind this page are all rights reserved. This file is the page itself, at its own address, in another format. It is not part of the CC BY 4.0 downloads listed at https://openbrokerapi.com/data. Quote from it with a link to the page. Cite as: cTrader ProtoOANewOrderReq. Broker API Hub, https://openbrokerapi.com/platforms/ctrader/messages/protooaneworderreq, newest check 2026-10-12. Where you rely on a single figure, cite the source and the checked date printed beside it as well. Where this page and a broker's own documentation differ, the documentation wins.