read

Security Notification – SSLv3 POODLE Vulnerability

As a security precaution Messente has disabled SSLv3 in our servers therefore Messente HTTP API is no more vulnerable to the POODLE exploit.

In most cases your Messente https:// API integration should already support secure TLS protocol and no action is needed for Messente HTTP API users.

You can also take a look at Scott Helme’s step-by-step guide on mitigating this vulnerability on multiple platforms, web servers and clients.

If you notice any issues with the API calls to Messente servers, please let us know at support@messente.com and we will help you with integration to new and secure TLS protocol.

Omni-channel messaging is here

Check out our latest webinar going over the details (plus a demo) of the intelligent A2P messaging API.
Learn more