Requests and urllib3 exception
Requests and urllib3 exception: requests.exceptions.JSONDecodeError
As text you can copy
requests.exceptions.JSONDecodeError - Kind
- Exception
- Where you meet it
- Raised in your own program by the library
What does requests.exceptions.JSONDecodeError mean in Requests and urllib3?
Requests could not decode the text into JSON. The documentation for Response.json() says it is raised if the response body does not contain valid JSON.
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.
What it means in trading API work
The body was not JSON: often empty, or an HTML error page from a gateway. Calling the json() method before checking the status is the usual way to meet it.
This part is this site's own explanation, written for people learning to call a trading API. It is not part of the source cited above and it describes no particular broker.
What should I do about requests.exceptions.JSONDecodeError?
Check the status code first, and log the status and the start of the body when decoding fails.
This page is an independent explanation in plain words. The definition itself is in the source it was read from, which is the authority if the two ever differ.