Match-Trader Platform API POST /manager/refresh-token
Renew the session token without logging in again. The reference says the refresh token travels as a cookie.
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. 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 lists two headers without a required mark and no body, and its example request sends no cookie header, although its text says the refresh token is included as a cookie. It lists no fields for the 200 reply. No mock reply is recorded.
Parameters
| Name | In | Type | Description |
|---|---|---|---|
| Acceptnot marked by the vendor | header | string | Example value application/json. |
| Content-Typenot marked by the vendor | header | string | Example value application/json. |
2 fields are tagged not marked by the vendor: Accept, Content-Type. 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.
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 as an environment variable first. Never paste real values into code.
# 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 = {
"Accept": "...",
"Content-Type": "application/json",
}
resp = requests.post(BASE_URL + "/manager/refresh-token", headers=headers, timeout=10)
resp.raise_for_status()
print(resp.json())JavaScript
// Set MATCH_TRADER_BASE_URL as an environment variable first. Never paste real values into code.
// 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 + "/manager/refresh-token", {
method: "POST",
headers: {
"Accept": "...",
"Content-Type": "application/json",
},
});
if (!res.ok) throw new Error(`HTTP ${res.status}`);
console.log(await res.json());curl
# Set MATCH_TRADER_BASE_URL as an environment variable first. Never paste real values into code.
# 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 POST "$MATCH_TRADER_BASE_URL/manager/refresh-token" \
-H "Accept: ..." \
-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
- 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.