Error codes

Match-Trader API error codes

3 decoded error codes for Match-Trader Platform API. Each page gives the exact error text and what it means. 1 of them carries a fix or a next step, and that row is marked Fix recorded. Where the source gives no remedy, the page says so.

Independent and unofficialNewest reading 9 Oct 2026

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.

HTTP 400

1 code

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.

HTTP 401

1 code

401 Unauthorized Fix recorded 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.

HTTP 410

1 code

410 Gone In the Match-Trader Platform API documentation, the example of a 410 response is plain text, not JSON.

How to cite this

Match-Trader API error codes. Broker API Hub, https://openbrokerapi.com/errors/match-trader, newest check 9 Oct 2026.

Where you rely on a single figure, cite the source and the checked date printed beside it as well.

Match-Trader API error codes

HTTP 400

HTTP 401

HTTP 410

More on the Match-Trader API

How to cite this