Broker API HubMenu

OANDA API POST /v3/accounts/{accountID}/orders

POST/v3/accounts/{accountID}/ordersversion v3Orders

Create an order. Market, limit, stop, market if touched and dependent orders all go through this one endpoint. Returns 201.

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.

Independent and unofficialdeveloper.oanda.comchecked

Confirmed on the official order endpoints page. Method, path and request parameters were re-read on that page on 12 Oct 2026 and agree with this record; the mock reply was not compared field by field. Success is HTTP 201, not 200; 400 means the order was rejected and the body carries orderRejectTransaction. Units are strings. Test on a practice account first.

Parameters

NameInTypeDescription
Accept-Datetime-FormatheaderstringOptional. RFC3339 (default) or UNIX for epoch seconds in datetime fields.
Content-TyperequiredheaderstringSend application/json on every request with a body.
accountIDrequiredpathstringAccount ID from GET /v3/accounts. Mock value shown.
orderrequiredbodyobjectThe order request. For a market order: type MARKET, instrument, units (positive to buy, negative to sell), timeInForce FOK, positionFill DEFAULT.

Authentication headers

NameTypeDescription
AuthorizationrequiredstringSend Bearer followed by your personal access token. Placeholder only: never paste a real token into this site.

Request

Written from the method, path and parameters recorded on this page, against the demo host. Not executed against a live or demo account. Credentials are read from environment variables on your own machine and are never entered on this site. The request builder writes these same snippets, from the same record.

This call takes a request body. The samples send it as JSON with a Content-Type of application/json (in Python, passing json= sets that header) and a placeholder for each of the 1 body field the record marks as required. Each placeholder has to be replaced with a real value before the request can succeed.

Python
# Set OANDA_TOKEN, OANDA_ACCOUNT_ID as environment variables first. Never paste real values into code.
# Optional and not shown: headers Accept-Datetime-Format.
import os
import requests

BASE_URL = "https://api-fxpractice.oanda.com"  # the demo host
headers = {
    "Authorization": "Bearer " + os.environ["OANDA_TOKEN"],
    "Content-Type": "application/json",
}
body = {"order": {}}
resp = requests.post(BASE_URL + "/v3/accounts/" + os.environ["OANDA_ACCOUNT_ID"] + "/orders", headers=headers, json=body, timeout=10)
resp.raise_for_status()
print(resp.json())
JavaScript
// Set OANDA_TOKEN, OANDA_ACCOUNT_ID as environment variables first. Never paste real values into code.
// Optional and not shown: headers Accept-Datetime-Format.
// Run as a module, for example a .mjs file, on a Node version that has fetch built in.
const BASE_URL = "https://api-fxpractice.oanda.com"; // the demo host
const res = await fetch(BASE_URL + "/v3/accounts/" + process.env.OANDA_ACCOUNT_ID + "/orders", {
  method: "POST",
  headers: {
    "Authorization": "Bearer " + process.env.OANDA_TOKEN,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({"order": {}}),
});
if (!res.ok) throw new Error(`HTTP ${res.status}`);
console.log(await res.json());
curl
# Set OANDA_TOKEN, OANDA_ACCOUNT_ID as environment variables first. Never paste real values into code.
# Optional and not shown: headers Accept-Datetime-Format.
curl -X POST "https://api-fxpractice.oanda.com/v3/accounts/$OANDA_ACCOUNT_ID/orders" \
  -H "Authorization: Bearer $OANDA_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"order": {}}'

Response

A mock response. The values are invented, so check field names against the official reference.

{
  "_mock": true,
  "orderCreateTransaction": {
    "id": "9002",
    "type": "MARKET_ORDER",
    "instrument": "EUR_USD",
    "units": "1000",
    "timeInForce": "FOK",
    "positionFill": "DEFAULT",
    "reason": "CLIENT_ORDER",
    "accountID": "101-004-MOCK-001",
    "time": "2026-09-18T08:00:02.000000000Z"
  },
  "orderFillTransaction": {
    "id": "9003",
    "type": "ORDER_FILL",
    "orderID": "9002",
    "instrument": "EUR_USD",
    "units": "1000",
    "price": "1.10020",
    "tradeOpened": {
      "tradeID": "9003",
      "units": "1000"
    },
    "accountID": "101-004-MOCK-001",
    "time": "2026-09-18T08:00:02.000000000Z"
  },
  "relatedTransactionIDs": [
    "9002",
    "9003"
  ],
  "lastTransactionID": "9003"
}

Response schema, HTTP 201

Every field this site's OpenAPI file for OANDA declares for this response.

FieldTypeDescription
orderCreateTransactionobjectNot recorded
idstringNot recorded
typestringNot recorded
instrumentstringNot recorded
unitsstringNot recorded
timeInForcestringNot recorded
positionFillstringNot recorded
reasonstringNot recorded
accountIDstringNot recorded
timestringNot recorded
orderFillTransactionobjectNot recorded
idstringNot recorded
typestringNot recorded
orderIDstringNot recorded
instrumentstringNot recorded
unitsstringNot recorded
pricestringNot recorded
tradeOpenedobjectNot recorded
tradeIDstringNot recorded
unitsstringNot recorded
accountIDstringNot recorded
timestringNot recorded
relatedTransactionIDsarray of stringNot recorded
lastTransactionIDstringNot recorded

Unverifiedno source opened This schema is not sourced to a page of the provider's own that we opened, so check field names against the official reference.

Limits that apply at OANDA

LimitValueScopeSource
Headline limit120/s per IP address, HTTP 429 above itipdeveloper.oanda.comchecked

OANDA API errors you may meet

All OANDA API error codes, including 236 more not listed here.