Announcing the end of HTTP support for Sinch Engage APIs

Sinch Engage is ending support for API requests sent over HTTP. If your integration connects using http:// addresses, change them to https://. It's a small change: your API, credentials and integration logic all stay the same.

Using a different API? These have their own articles:

• SOAP and XML APIs: Announcing the end of HTTP support for the Sinch Engage SOAP and XML APIs

• MessageNet API: Announcing the end of HTTP support for the MessageNet API

If you use an API that isn't listed in this article, it isn't covered here.

• This is not a migration to a new API.

• Your existing credentials and integration logic stay the same.

• Your account, numbers and pricing stay the same.

HTTPS encrypts the traffic between your system and ours. HTTP doesn't, which means anything sent over it, including your credentials and your customers' message content, can be read by others on the network. HTTPS is the industry standard for securing API traffic. Ending HTTP support helps keep your data safe and meets modern security requirements.

1. Check your integration. Look through your code, configuration files and settings for any http:// address that points to one of the APIs listed above.

2. Update the address. Change http:// to https://. For example, http://api.messagemedia.com becomes https://api.messagemedia.com. You can find your account's API Base URL in API Settings.

3. Check your system supports TLS 1.2 or higher. We support TLS 1.2 and 1.3 and recommend TLS 1.3. See Security Best Practices for Sinch Engage API Integration.

4. Test your integration. Send a test message and check that it works as expected.

5. Make the change before the date for your API in the table above.

These APIs are being switched off on 29 October 2027. Switching to HTTPS keeps you sending for now, but you'll need to move to the Sinch Engage REST API before then. If you're updating your integration anyway, it may be easier to move to the REST API now. See Announcing the removal of the legacy Mobipost, DirectSMS, SMS Broadcast and Streetdata APIs and the REST API migration guide for your API.

You're affected if any system sends requests to one of the APIs listed above using http://. Check for:

• http:// in your code or settings. Search your code, environment variables and configuration files for our API addresses.

• A plugin or third-party app. If you connect another product (for example a CRM, booking system or website plugin) to your account, it may be using HTTP.

• Scripts and scheduled jobs. Older scripts and automated tasks are easy to miss.

• A message from us. We're contacting customers whose integrations we've identified as using HTTP.

If you have more than one account, check each one. Not sure? Contact our Support team.

After the date for your API:

• Requests sent over HTTP will time out or fail, and the messages in them won't be sent.

• Automated messages, such as appointment reminders, alerts or verification codes, will stop. If your system doesn't check for errors or timeouts, this may happen without you noticing.

We can't make exceptions for individual accounts. We strongly recommend making the change as soon as you can.

Which date applies to me?
It depends on the API address your integration uses. Check the table at the top of this article.

I use the SOAP, XML or MessageNet API. Does this article apply to me?
No. Those APIs have their own articles, linked above.

Do I need a new API key or new credentials?
No. Your existing credentials work over HTTPS exactly as they do now.

Do I need to change how my integration works?
No. You only need to change http:// to https:// in your API addresses. Your requests, responses and integration logic stay the same.

I already use HTTPS. Do I need to do anything?
No.

I use a plugin, app or outside developer to connect to your service. What should I do?
Contact the provider or developer and ask them to switch to HTTPS before the date for your API. Share this article with them.

I only use the web app. Do I need to do anything?
No. Sending and receiving messages in the web app isn't affected.

Can I get an extension?
No. We can't make exceptions for individual accounts.

If you need help updating your integration, contact our Support team or speak to your account representative. See also Security Best Practices for Sinch Engage API Integration.