Broker API errors by HTTP status
The same status means different things at different brokers. These pages put the decoded errors for one status side by side, drawn from 1,776 error records.
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 400Bad Request. 186 decoded, from 11 brokers and platforms, with the standard's general record
- HTTP 401Unauthorized. 39 decoded, from 11 brokers and platforms, with the standard's general record
- HTTP 403Forbidden. 22 decoded, from 7 brokers and platforms, with the standard's general record
- HTTP 404Not Found. 22 decoded, from 8 brokers and platforms, with the standard's general record
- HTTP 405Method Not Allowed. 2 decoded, from 2 brokers and platforms, with the standard's general record
- HTTP 409Conflict. 5 decoded, from 3 brokers and platforms, with the standard's general record
- HTTP 429Too Many Requests. 7 decoded, from 7 brokers and platforms, with the standard's general record
- HTTP 500Internal Server Error. 11 decoded, from 5 brokers and platforms, with the standard's general record
- HTTP 503Service Unavailable. 3 decoded, from 2 brokers and platforms, with the standard's general record
What is and is not here
A status gets a page when decoded errors from two or more brokers or platforms return it, so that there is something to compare. 1,423 error records carry no HTTP status in this dataset. They are on the error pages by broker.