Broker API HubMenu

TLS alert

TLS alert: bad_certificate

As text you can copy

bad_certificate
Kind
Alert
Where you meet it
While a secure connection is being set up or used
Read from
RFC 8446, The Transport Layer Security (TLS) Protocol Version 1.3, section 6.2

What does bad_certificate mean in TLS?

A certificate was corrupt, contained signatures that did not verify correctly, or had a similar fault.

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.

Independent and unofficialrfc-editor.orgchecked

What it means in trading API work

If the server sends this alert, it is complaining about a client certificate you presented. If your own client raises it, the server's certificate did not check out, which can mean that a proxy or a security product is intercepting the connection.

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 bad_certificate?

Where the API uses client certificates, check that the certificate and key files are the right ones and intact. Otherwise find out what stands between you and the server. Do not disable verification.

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.