Errors that belong to no broker
TLS alerts explained
5 entries decoded. These are alerts one side of a secure connection sends when it cannot set the connection up or accept a certificate. 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: RFC 8446, The Transport Layer Security (TLS) Protocol Version 1.3.
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.
Alerts
5 entries
While a secure connection is being set up or used.
bad_A certificate was corrupt, contained signatures that did not verify correctly, or had a similar fault.certificate certificate_A certificate has expired or is not currently valid.expired handshake_The sender was unable to negotiate an acceptable set of security parameters given the options available.failure protocol_The protocol version the other side tried to negotiate is recognised but not supported.version unknown_A valid certificate chain or partial chain was received, but the certificate was not accepted because the CA certificate could not be located or could not be matched with a known trust anchor.ca
How to cite this
TLS alerts explained. Broker API Hub, https://openbrokerapi.com/errors/tls, newest check .
Where you rely on a single figure, cite the source and the checked date printed beside it as well.