overview

The Orders service is Tradara’s Order Management System (OMS). It accepts order intents from your application, runs them through pre-trade risk, routes them to the matching venue, and emits lifecycle events you can subscribe to. All orders are scoped to a single account_id that was provisioned via the Prop Firm API. The same firm API key can place orders across any account belonging to the firm.

Base path

/v1/orders

What lives here

Page	Purpose
Place an order	`POST /v1/orders` — full request schema, idempotency, and validation.
Order types	MARKET, LIMIT, STOP, STOP_LIMIT, TRAILING_STOP, TRAILING_STOP_LIMIT.
Time in force	DAY, GTC, IOC, FOK, GTD.
Lifecycle	State diagram from PENDING through FILLED, including cancel/modify branches.
Modify and cancel	PATCH, single cancel, cancel-all, flatten, close-all.
Order groups	OCO, OTO, OTOCO, and OCO link/companion helpers.
List and get	Cursor pagination and filters.
Realtime WebSocket	Live `orders.state` and `orders.ack` events on `/v1/ws`.
Errors	Reference for 400/403/404/409/422/502 responses.

Quick example

curl -X POST https://api.tradara.com/v1/orders \
  -H "X-Tradara-Api-Key: $TRADARA_API_KEY" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{
    "account_id": "'"$ACCOUNT_ID"'",
    "instrument_id": "'"$INSTRUMENT_ID"'",
    "side": "BUY",
    "execution_type": "MARKET",
    "quantity": "1"
  }'

Fills — execution-level records produced as orders fill.
Positions — net exposure after fills are booked.
Trades — round-trip OPEN/CLOSED records.

Orders

Fills

Positions

Trades

Balances

Realtime WebSocket

overview

Base path

What lives here

Quick example

​Base path

​What lives here

​Quick example

​Related

Base path

What lives here

Quick example

Related