We’re announcing an upcoming security update to the Bridge API (api.bridgedataoutput.com).
What’s changing
On November 3, 2026, we will update the TLS protocols and ciphers supported by our API, moving to a more modern security policy.
- TLS 1.0 and TLS 1.1 will no longer be supported. Connections must use TLS 1.2 or higher.
- Several older, weaker cipher suites (primarily SHA-1 and legacy CBC-based ciphers, and 3DES) will be removed.
The cipher suites being removed are:
- ECDHE-ECDSA-AES128-SHA256
- ECDHE-ECDSA-AES128-SHA
- ECDHE-ECDSA-AES256-SHA384
- ECDHE-ECDSA-AES256-SHA
- ECDHE-RSA-AES128-SHA256
- ECDHE-RSA-AES128-SHA
- ECDHE-RSA-AES256-SHA384
- ECDHE-RSA-AES256-SHA
- AES128-GCM-SHA256
- AES256-GCM-SHA384
- AES128-SHA256
- AES256-SHA
- AES128-SHA
- DES-CBC3-SHA
Who is affected
The vast majority of clients negotiate TLS 1.2+ with a modern cipher and will see no change. You may be affected if you connect from an older operating system or runtime, such as Windows Server 2012 R2 or earlier, or an outdated .NET / HTTP library. Clients that only support TLS 1.0/1.1 or one of the ciphers above will fail their TLS handshake and be unable to connect after November 3.
What you should do
Test now against our UAT environment, which is already running the updated security policy: uat.bridgedataoutput.com
If your integration connects and works against UAT, no action is needed. If it fails, update your OS, runtime, or TLS library to one that supports TLS 1.2+ with a modern cipher suite before November 3, 2026.
If you have questions or run into trouble testing, contact us at support@bridgeinteractive.com and we’ll be glad to help.