Match-Trader Platform API GET /mtr-api/{SYSTEM_UUID}/active-orders

GET/mtr-api/{SYSTEM_UUID}/active-ordersOrder

List the pending orders on the trading account that have not yet been executed.

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 unofficialapp.theneo.iochecked 12 Oct 2026

Read on 12 Oct 2026 in Match-Trade's Platform API reference, which the Match-Trade documentation site links to and which is published at app.theneo.io. This call sits in a section the page loads only when it is opened, so its content was read from the data the page itself requests for that section. The method, path, parameters and required marks are the reference's own. The reference gives one base address, a sandbox at https://mtr-demo-prod.match-trader.com, and none for a broker's own platform. The reference writes the address with the bare word SYSTEM_UUID where the trading system's identifier goes, and its text calls the value systemUUID. This record writes it as a path parameter. Each entry of orders carries id, symbol, alias, volume, type, creationTime, activationPrice, side, stopLoss, takeProfit and comment. No mock reply is recorded.

Parameters

Name	In	Type	Description
SYSTEM_UUIDrequired	path	string	The identifier of the trading system the account is on. The reference does not say where to read it. The login reply carries a system object with a uuid under each trading account's offer.
Cookierequired	header	string	Marked required, with the example value co-auth={token}. The login section says the token field of the login reply is passed as a cookie, and the Market Watch section describes this header as tradingAccountToken.token.
Content-Typerequired	header	string	Marked required. The example value is application/json.

Authentication headers

Name	Type	Description
Auth-trading-apirequired	string	The tradingApiToken of the trading account, from the login reply. Marked required. Placeholder only: never paste a real token into this site.

Request

Written from the method, path and parameters recorded on this page. No demo host is recorded as a plain address for this API, so the samples read the base address from an environment variable. 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.

Python

# Set MATCH_TRADER_BASE_URL, MATCH_TRADER_TRADING_API_TOKEN, MATCH_TRADER_TOKEN as environment variables first. Never paste real values into code.
# MATCH_TRADER_TRADING_API_TOKEN and MATCH_TRADER_TOKEN hold the Auth-trading-api and Cookie headers that POST /manager/mtr-login returns.
# No demo host is recorded as a plain address for this API, so the base address is read from MATCH_TRADER_BASE_URL.
# Replace each {placeholder}, "..." and 0 with a real value before running.
import os
import requests

BASE_URL = os.environ["MATCH_TRADER_BASE_URL"]
headers = {
    "Auth-trading-api": os.environ["MATCH_TRADER_TRADING_API_TOKEN"],
    "Cookie": "co-auth=" + os.environ["MATCH_TRADER_TOKEN"],
    "Content-Type": "application/json",
}
resp = requests.get(BASE_URL + "/mtr-api/{SYSTEM_UUID}/active-orders", headers=headers, timeout=10)
resp.raise_for_status()
print(resp.json())

JavaScript

// Set MATCH_TRADER_BASE_URL, MATCH_TRADER_TRADING_API_TOKEN, MATCH_TRADER_TOKEN as environment variables first. Never paste real values into code.
// MATCH_TRADER_TRADING_API_TOKEN and MATCH_TRADER_TOKEN hold the Auth-trading-api and Cookie headers that POST /manager/mtr-login returns.
// No demo host is recorded as a plain address for this API, so the base address is read from MATCH_TRADER_BASE_URL.
// Replace each {placeholder}, "..." and 0 with a real value before running.
// Run as a module, for example a .mjs file, on a Node version that has fetch built in.
const BASE_URL = process.env.MATCH_TRADER_BASE_URL;
const res = await fetch(BASE_URL + "/mtr-api/{SYSTEM_UUID}/active-orders", {
  method: "GET",
  headers: {
    "Auth-trading-api": process.env.MATCH_TRADER_TRADING_API_TOKEN,
    "Cookie": "co-auth=" + process.env.MATCH_TRADER_TOKEN,
    "Content-Type": "application/json",
  },
});
if (!res.ok) throw new Error(`HTTP ${res.status}`);
console.log(await res.json());

curl

# Set MATCH_TRADER_BASE_URL, MATCH_TRADER_TRADING_API_TOKEN, MATCH_TRADER_TOKEN as environment variables first. Never paste real values into code.
# MATCH_TRADER_TRADING_API_TOKEN and MATCH_TRADER_TOKEN hold the Auth-trading-api and Cookie headers that POST /manager/mtr-login returns.
# No demo host is recorded as a plain address for this API, so the base address is read from MATCH_TRADER_BASE_URL.
# Replace each {placeholder}, "..." and 0 with a real value before running.
curl -X GET "$MATCH_TRADER_BASE_URL/mtr-api/{SYSTEM_UUID}/active-orders" \
  -H "Auth-trading-api: $MATCH_TRADER_TRADING_API_TOKEN" \
  -H "Cookie: co-auth=$MATCH_TRADER_TOKEN" \
  -H "Content-Type: application/json"

Response

No mock response is recorded for this endpoint. Where the record says why, or names the fields of the reply, it does so in the note at the top of this page. That is a statement about this record, not about what the API returns: read the shape of the reply in the official reference.

Match-Trader API errors you may meet

All Match-Trader API error codes.