Starting October 22, 2026, the Sarbacane API will require exclusive use of the secure HTTPS protocol and support for TLS 1.2 or higher. If your integrations already use HTTPS and an up-to-date technical environment, no action is required. Otherwise, you must update your requests before this date to avoid any service interruption.
Have an integration or applications that call the Sarbacane API.
Have access to the source code or technical configuration of your servers.
Have a plan that allows you to use the API
Have the rights required to use the API
Starting October 22, 2026, the Sarbacane API servers will enforce two strict security requirements:
Exclusive use of HTTPS: requests sent over unencrypted HTTP (http://) will be permanently rejected.
Support for TLS 1.2 or higher: only connections using TLS version 1.2 or higher and modern cipher suites will be accepted.
To ensure your services continue uninterrupted, perform the following checks before October 22, 2026:
In your application code, check that the root URL for all your Sarbacane API calls uses the https:// prefix (not http://).
Check that your server, programming language, and HTTP libraries support TLS 1.2 or higher.
Perform a send and receive test in your staging environment before the deadline.
Important : requests made over HTTP or using a TLS version earlier than 1.2 will be rejected starting October 22, 2026, causing your API calls to fail.
Your API calls continue to run without interruption and receive the usual responses from the Sarbacane platform.
Your API calls fail or return an SSL/TLS connection error Check that your application is not pointing to an http:// address and update your server's technical components (e.g., OpenSSL, cURL HTTP libraries) to recent versions compatible with TLS 1.2 or higher.
