Support Center

HTTP to HTTPS Redirection

Last Updated: Jun 16, 2016 04:35PM AEST
Redirection from HTTP to HTTPS
As part of our ongoing commitment to improving service and increasing security, we will be redirecting all web requests to the secure HTTPS protocol as of June 30th, 2016.

This means that all service offerings including our website and HTTP API, will only be accessible through the HTTPS protocol. Any request sent to a non-secure HTTP URL will be redirected to a secure HTTPS URL.

In addition to our HTTPS protocol update, we will be redirecting all website URLs without the 'www' prefix to an address with it. This change will affect customers who are currently using a HTTP API without the 'www' prefix. The web server will redirect the requests to the URL with a 'www' prefixed.
Here is an example of how the secure URL will be displayed in your browseretc

 *Please note this will not affect customers using browsers to access our services.

Benefits of both these adjustments include a significant improvement in user data security, as well as standardization of connection to our system which will allow for greater future flexibility and minimize disruptions for maintenance.

Client-side Adjustments

If you are currently utilizing the HTTP API you will need to make a small alteration to your API URL.
To do this you can simply change your API URL manually to HTTPS, or enable redirects in your client library.

Current URL: http:// (etc)

Modified URL: (etc)
We recommend this information be forwarded to the appropriate technical resource within your business to implement the required changes.

If you are unsure on how this will affect your business, or would like more information about the switch to HTTPS, we encourage you to get in contact with our Customer Success Team for more information.

No changes are required if you are connecting to us via the SMPP API. The SMPP connection is bound on the domain ( with port 1775 rather than the HTTP/HTTPS ports of 80/443 .

Contact Us

seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
Invalid characters found