Announcing the end of HTTP support for the MessageNet API

We're permanently ending support for insecure HTTP connections to the MessageNet API. From 25 March 2027, requests sent over HTTP won't be processed. Requests sent over HTTPS aren't affected.

This article covers the MessageNet API only. For our other APIs, see Announcing the end of HTTP support for Sinch Engage APIs.

• The MessageNet API isn't being retired as part of this change. This is not a migration to a new API.

• Your 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, so anything sent over it, including your credentials and your customers' message content, can be read by others on the network. 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 the MessageNet API.

2. Update the address. Change http:// to https://.

3. Check your system supports TLS 1.2 or higher. We support TLS 1.2 and 1.3 and recommend TLS 1.3. TLS 1.0 and 1.1 aren't supported. Older systems and libraries may need updating. See Security Best Practices for Sinch Engage API Integration.

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

5. Make the change before 25 March 2027.

You're affected if any system sends requests to the MessageNet API using http://. Check for:

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

• A plugin or third-party app. If another product (for example a practice management, booking or CRM system) sends messages through 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.

From 25 March 2027:

• Requests sent over HTTP to the MessageNet API 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'll send reminders as the date gets closer. We strongly recommend making the change as soon as you can.

I was told HTTP support would end on 30 October 2026. Which date is right?
25 March 2027 is the date for the MessageNet API, due to customer feedback. Please still switch to HTTPS as soon as you can.

Do I need 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 the API address. Your requests, responses and integration logic stay the same.

Is the MessageNet API being retired?
Not as part of this change. Only HTTP connections are ending. You can keep using the MessageNet API over HTTPS.

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 your provider or developer and ask them to switch to HTTPS before 25 March 2027. 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.

If you need help updating your integration, contact our Support team or speak to your account representative.