Match-Trader Platform API POST /mtr-api/{SYSTEM_UUID}/pending-order/edit
Change a pending order: its price, volume, stop loss or take profit.
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.
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. The reference marks the headers as required and gives the body fields without a mark, so it does not say whether id, instrument, orderSide, type and volume must be sent. The price field is named priceOrder here and price in the call that creates the order. The reference lists no reply fields for this call. 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. |
| idnot marked by the vendor | body | string | The identifier of the order. |
| instrumentnot marked by the vendor | body | string | The symbol. |
| orderSidenot marked by the vendor | body | string | BUY or SELL. |
| typenot marked by the vendor | body | string | The order type. Example value LIMIT. |
| volumenot marked by the vendor | body | number | The order's volume. |
| priceOrderrequired | body | number | The order's price. The reference says it cannot be null, which is why it is recorded as required. |
| slPricerequired | body | number | Stop loss price. The reference says it cannot be null and that 0 is sent when none is wanted, which is why it is recorded as required. |
| tpPricerequired | body | number | Take profit price. The reference says it cannot be null and that 0 is sent when none is wanted, which is why it is recorded as required. |
| isMobilenot marked by the vendor | body | boolean | Example value false. |
6 fields are tagged not marked by the vendor: id, instrument, orderSide, type, volume, isMobile. The vendor's page lists them and marks them neither required nor optional. That describes the page, not a test of what the host accepts, so the samples send them with a placeholder.
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.
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 3 body fields the record marks as required, and a placeholder for each of the 6 body fields the vendor's page marks neither required nor optional, named in the sample's own comment. Each placeholder has to be replaced with a real value before the request can succeed.
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.
# Not marked required or optional on the vendor's page, so sent here with a placeholder: id, instrument, orderSide, type, volume, isMobile. Leave out any the call does not need.
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",
}
body = {"id": "...", "instrument": "...", "orderSide": "...", "type": "...", "volume": 0, "priceOrder": 0, "slPrice": 0, "tpPrice": 0, "isMobile": False}
resp = requests.post(BASE_URL + "/mtr-api/{SYSTEM_UUID}/pending-order/edit", headers=headers, json=body, 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.
// Not marked required or optional on the vendor's page, so sent here with a placeholder: id, instrument, orderSide, type, volume, isMobile. Leave out any the call does not need.
// 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}/pending-order/edit", {
method: "POST",
headers: {
"Auth-trading-api": process.env.MATCH_TRADER_TRADING_API_TOKEN,
"Cookie": "co-auth=" + process.env.MATCH_TRADER_TOKEN,
"Content-Type": "application/json",
},
body: JSON.stringify({"id": "...", "instrument": "...", "orderSide": "...", "type": "...", "volume": 0, "priceOrder": 0, "slPrice": 0, "tpPrice": 0, "isMobile": false}),
});
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.
# Not marked required or optional on the vendor's page, so sent here with a placeholder: id, instrument, orderSide, type, volume, isMobile. Leave out any the call does not need.
curl -X POST "$MATCH_TRADER_BASE_URL/mtr-api/{SYSTEM_UUID}/pending-order/edit" \
-H "Auth-trading-api: $MATCH_TRADER_TRADING_API_TOKEN" \
-H "Cookie: co-auth=$MATCH_TRADER_TOKEN" \
-H "Content-Type: application/json" \
-d '{"id": "...", "instrument": "...", "orderSide": "...", "type": "...", "volume": 0, "priceOrder": 0, "slPrice": 0, "tpPrice": 0, "isMobile": false}'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
- 400HTTP 400. In the Match-Trader Platform API documentation, the Errors section, which it describes as examples of error responses for each status code, lists status 400 but shows no example body and no description for it.
- 401 UnauthorizedHTTP 401. In the Match-Trader Platform API documentation, the example of a 401 response has the title "Unauthorized" and the detail "Authorization information is missing or invalid." (the vendor's wording), with the status, the request path and a timestamp.
- 410 GoneHTTP 410. In the Match-Trader Platform API documentation, the example of a 410 response is plain text, not JSON.