TradeLocker API error code
TradeLocker API error: 400 Bad Request
What does 400 Bad Request mean on the TradeLocker API?
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. The reference gives the status no further description.
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.
No fix in the source
The vendor's page gives no remedy. Check the request against the fields the reference documents for the route.
That is all the source says, so this page does not invent a fix. General guidance: what HTTP 400 means and how other APIs use it, the other errors with HTTP 400 recorded for TradeLocker, and the error lookup for the exact text of the reply you received.