TradeLocker API DELETE /trade/orders/{orderId}
Cancel one pending order. It works only before the order has 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.
Read on 12 Oct 2026 on TradeLocker's own reference page for this call, in the Markdown version the documentation site serves at the same address with .md on the end. That page carries the call's OpenAPI definition, headed Trading API version 2.11.0: the method, path, parameters and required marks here are that definition's. The reference names the optional header developer-api-key, while TradeLocker's getting started page calls the Developer Program key tl-developer-api-key and says it unlocks less restrictive rate limits. This record keeps the name on the reference page. Documented success statuses are 200, with a status s of ok, and 204. No mock reply is recorded.
Parameters
| Name | In | Type | Description |
|---|---|---|---|
| orderIdrequired | path | integer | The identifier of the order, as returned when it was placed. |
| accNumrequired | header | integer | The account number that selects which of the login's accounts the call acts on. It is the accNum from GET /auth/jwt/all-accounts, not the accountId. |
Authentication headers
| Name | Type | Description |
|---|---|---|
| Authorizationrequired | string | Send Bearer followed by the accessToken from POST /auth/jwt/token. The reference marks the call as secured by a bearer JWT. Placeholder only: never paste a real token into this site. |
| developer-api-key | string | A key issued through the TradeLocker Developer Program. Optional. |
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.
Python
# Set TRADELOCKER_ACCESS_TOKEN, TRADELOCKER_ACC_NUM as environment variables first. Never paste real values into code.
# TRADELOCKER_ACCESS_TOKEN holds the Authorization header that POST /auth/jwt/token returns.
# Replace each {placeholder}, "..." and 0 with a real value before running.
# Optional and not shown: headers developer-api-key.
import os
import requests
BASE_URL = "https://demo.tradelocker.com/backend-api" # the demo host
headers = {
"Authorization": "Bearer " + os.environ["TRADELOCKER_ACCESS_TOKEN"],
"accNum": os.environ["TRADELOCKER_ACC_NUM"],
}
resp = requests.delete(BASE_URL + "/trade/orders/{orderId}", headers=headers, timeout=10)
resp.raise_for_status()
print(resp.json())JavaScript
// Set TRADELOCKER_ACCESS_TOKEN, TRADELOCKER_ACC_NUM as environment variables first. Never paste real values into code.
// TRADELOCKER_ACCESS_TOKEN holds the Authorization header that POST /auth/jwt/token returns.
// Replace each {placeholder}, "..." and 0 with a real value before running.
// Optional and not shown: headers developer-api-key.
// Run as a module, for example a .mjs file, on a Node version that has fetch built in.
const BASE_URL = "https://demo.tradelocker.com/backend-api"; // the demo host
const res = await fetch(BASE_URL + "/trade/orders/{orderId}", {
method: "DELETE",
headers: {
"Authorization": "Bearer " + process.env.TRADELOCKER_ACCESS_TOKEN,
"accNum": process.env.TRADELOCKER_ACC_NUM,
},
});
if (!res.ok) throw new Error(`HTTP ${res.status}`);
console.log(await res.json());curl
# Set TRADELOCKER_ACCESS_TOKEN, TRADELOCKER_ACC_NUM as environment variables first. Never paste real values into code.
# TRADELOCKER_ACCESS_TOKEN holds the Authorization header that POST /auth/jwt/token returns.
# Replace each {placeholder}, "..." and 0 with a real value before running.
# Optional and not shown: headers developer-api-key.
curl -X DELETE "https://demo.tradelocker.com/backend-api/trade/orders/{orderId}" \
-H "Authorization: Bearer $TRADELOCKER_ACCESS_TOKEN" \
-H "accNum: $TRADELOCKER_ACC_NUM"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.
TradeLocker API errors you may meet
- 400 Bad RequestHTTP 400. TradeLocker lists 400 with the description "Bad Request" as a response of its authentication routes: POST /auth/jwt/token, which fetches the JWT tokens, POST /auth/jwt/refresh and GET /auth/jwt/all-accounts.
- 401 UnauthorizedHTTP 401. TradeLocker lists 401 with the description "Unauthorized" as a response of its /trade routes, including placing, modifying and cancelling orders.
- 403 ForbiddenHTTP 403. TradeLocker lists 403 with the description "Forbidden" as a response of its /trade routes, including placing, modifying and cancelling orders.
- 404 Not FoundHTTP 404. TradeLocker lists 404 with the description "Not Found" as a response of many /trade routes, including placing an order, closing all positions and the account, instrument, configuration and history routes.
- no_dataA status in the response of GET /trade/history, not an HTTP error.