Errors that belong to no broker
curl exit codes explained
7 entries decoded. These are the codes curl and libcurl report when a request fails before a usable reply arrives. Each page says what the entry means, what it means in trading API work and what to do next, and links to the place it is defined: libcurl error codes.
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.
Exit codes
7 entries
The exit status of the command.
CURLE_Failed to connect to the host or proxy.COULDNT_ CONNECT (7) CURLE_Could not resolve host: the remote host given was not resolved.COULDNT_ RESOLVE_ HOST (6) CURLE_Nothing was returned from the server, and under the circumstances getting nothing is considered an error.GOT_ NOTHING (52) CURLE_Operation timeout: the time-out period specified was reached according to the conditions.OPERATION_ TIMEDOUT (28) CURLE_The remote server's SSL certificate or SSH fingerprint was deemed not OK.PEER_ FAILED_ VERIFICATION (60) CURLE_Failure with receiving network data.RECV_ ERROR (56) CURLE_A problem occurred somewhere in the SSL/TLS handshake.SSL_ CONNECT_ ERROR (35)
How to cite this
curl exit codes explained. Broker API Hub, https://openbrokerapi.com/errors/curl, newest check .
Where you rely on a single figure, cite the source and the checked date printed beside it as well.