Deprecated - please use the JSON API instead.

Transport Layer Requirements

As part of our ongoing system improvements, this API will be migrated to new infrastructure. The changes have been designed to be transparent to API users and should not impact most customers.

We would like to assure you that any existing endpoint you are using will not be removed. If you are using a custom system integration with unconventional connection methods or particularly old software to connect to this API, your integration might be affected and require minor changes in order to continue working. Please see the table at the bottom of this page for technical details.

We will provisionally begin migrating customers over on Thu, 15 July 2021, in a phased approach over a period of time.

As part of this migration, two new endpoints have been made available. These new endpoints can be used immediately and we strongly recommend you switch to one of these as the preferred method of connecting to this API. These endpoints will be HTTPS-only (no unencrypted traffic) and will have many benefits over existing endpoints. Refer to the “New EAPI endpoints” tables below to see which endpoint you should switch to based on the current endpoint in use, as well as important technical changes:


New EAPI endpoints

current new
bulksms.2way.co.za api-legacy1.bulksms.com
community.bulksms.com api-legacy1.bulksms.com
bulksms.vsms.net api-legacy2.bulksms.com
www.bulksms.co.uk api-legacy2.bulksms.com
usa.bulksms.com api-legacy2.bulksms.com
bulksms.com.es api-legacy2.bulksms.com
bulksms.de api-legacy2.bulksms.com
community.bulksms.co.uk api-legacy2.bulksms.com


feature current endpoint new endpoint notes
Automatic failover not supported supported Reliability improvements
TLS versions supported SSLv3, 1.0 1.2, 1.3 Security improvements
Location Africa/Europe Global Performance improvements
Endpoint IP address static dynamic Note the change to dynamic addresses
Unencrypted HTTP supported not supported Note the removal of support for unencrypted connections
HTTP versions supported HTTP/1.1 HTTP/1.1, HTTP/2 Note the introduction of HTTP/2 support
SNI support requirement not required required Note SNI becomes a requirement
RC4 support supported not supported Note RC4 support is being removed
Weak Diffie-Hellman key exchange support supported not supported Note DH key exchange requirements being upgraded


If you cannot support a change to the new hostname for this API at this moment, or cannot support one or more of the technical changes on the new endpoint, please see the “Current EAPI endpoints” table below for important technical changes expected on the current hostnames from the migration date onwards:


Current EAPI endpoints

feature before after notes
Automatic failover not supported not supported No reliability improvements
TLS versions supported SSLv3, 1.0 1.0, 1.1, 1.2, 1.3 Security improvements
Location Africa/Europe Africa/Europe No performance improvements
Endpoint IP address static static Current endpoints retain static addresses
Unencrypted HTTP supported supported Customers are strongly advised to migrate to HTTPS on the new endpoints. HTTP is deprecated and will be removed in the future
SNI support requirement not required required for TLS only Note SNI becomes a requirement for TLS-encrypted connections
HTTP versions supported HTTP/1.1 HTTP/1.1, HTTP/2 Note the introduction of HTTP/2 support
RC4 support supported not supported Note RC4 support is being removed
Weak Diffie-Hellman key exchange support supported not supported Note DH key exchange requirements being upgraded


If you have you questions or concerns regarding these changes, please contact us.