Support – 8x8 CPaaS Help Center

Mandatory Security Update: TLS 1.3 Requirement for Singapore SMS Traffic
Overview

To align with the nationwide security mandate issued by the Infocomm Media Development Authority (IMDA) of Singapore, 8x8 is enforcing a minimum encryption standard of TLS 1.3 for all connections transmitting SMS traffic into the Singapore region.

This requirement applies to both HTTP API and SMPP integrations and became effective as of April 1, 2026.

Technical Specifications by Connection Type

1. For HTTP API Customers

Connections attempting to utilize legacy encryption protocols (TLS 1.2 or lower) will be rejected at the gateway with the following response:
- HTTP Status Code: 426 Upgrade Required
- Error Code: 1014
- Description: TLS 1.3+ is required for Singapore-bound messages.
2. For SMPP Customers

To remain compliant, SMPP clients must transition away from unencrypted ports and legacy TLS versions.
- Required Protocol: TLS 1.3
- Required Port: 2776 (TLS Encrypted)
- Note: Connections to the unencrypted port 2775 or connections using TLS 1.2 on port 2776 will be terminated for Singapore-bound traffic.
Required Actions

Step 1: Technical Review

Coordinate with your DevOps or Engineering team to audit your current integration settings:
- HTTP Users: Verify that your API client is configured to negotiate TLS 1.3.
- SMPP Users: Check your SMPP server settings to confirm the destination port and encryption protocol.
Step 2: Protocol Upgrade & Re-routing
- HTTP Users: Promptly switch your connection protocol to TLS 1.3.
- SMPP Users: Update your configuration to use Port 2776 with TLS 1.3 encryption enabled.
Step 3: Validation

After updating your settings, we recommend performing a test submission to a Singapore destination to verify successful connectivity.
- HTTP: Confirm receipt of a standard 200 OK or Accepted response.
- SMPP: Ensure a successful BIND_TRANSMITTER or BIND_TRANSCEIVER PDU is established over the encrypted port.
Frequently Asked Questions (FAQ)

Why is this mandatory? This is a nationwide mandate by the Singapore government (IMDA) to protect the mobile ecosystem from cybersecurity threats. All service providers must enforce these standards to terminate traffic into the country.

What happens if I don't upgrade?

All non-compliant traffic (Unencrypted or TLS 1.2) toward Singapore will be blocked. This is a hard-stop requirement to meet IMDA regulatory standards.

Does this affect traffic to other countries?

While 8x8 recommends TLS 1.3 for all global traffic to ensure maximum security, this specific "hard-block" currently applies only to the Singapore route.

Support and Assistance

If your team requires specific technical documentation regarding 8x8’s TLS 1.3 endpoints for HTTP or SMPP, please contact our support team:
- Email: cpaas-support@8x8.com
Can I Whitelist my IPs (For HTTP/API calls)?
With 8x8, your communication is secure, even in the unlikely event that someone gets hold of your API key. That's because only authorized devices from your approved locations (whitelisted IPs) can access our platform.

You can set this up using you 8x8 Connect portal here https://connect.8x8.com/messaging/api-keys

Under IP Whitelisting section. You may Create IP Address

You will be prompted to input the below information. Click SAVE once done.
How do I subscribe to your Status Page
Subscribe to Updates

There are multiple channels available to subscribe to our Status Page.
- Subscribe via Email
- Subscribe via Text Message
- Subscribe via Slack
- Subscribe via Webhook
- Subscribe via Atom or RSS Feed
Subscribe to Components

As a subscriber, you are able to select which Components you want to receive updates for. In this way, you will only be receiving update for Products.

Aside from our CPaaS products, we are also posting any interruptions , maintenance or any activities done by our External Partner Operators. This can be found under External Connectivity.

You may select which region is relevant to your traffic.
How do I check my SMS Error Codes on the customer portal?
Error codes are numeric codes used to signify that something unexpected or unwanted has occurred while sending your SMS.

Think of them like warnings or alerts – they tell you something went wrong, but they also usually point you in the right direction to identify the cause and fix it.

You can find this information in the Connect Portal under SMS > Logs Section.

You may encounter messages failing, this is indicated with the status Undelivered. By expanding each transaction, you can see additional information of Error Code and Code Description.

**Some transactions of Undelivered status may not show corresponding Error Code and Error Code Description. This is due to no Error data from our SMS Partner
Can I register for a Sender ID?
To request for Sender ID registration, please approach your Account Manager or drop an email to support@wavecell.com.

Please note that Sender ID registrations are not applicable to all countries and it is subjected to individual operator's policies.
Do you have a Status Page?
8x8 CPaaS has a status page. You may visit the page here : https://status.wavecell.com/

Our status page has 2 sections.

1. Service Availability

In the Service Availability section, you can see the different Components of our 8x8 CPaaS products.
- SMS
- Chat Apps (Whatsapp, Viber and Other Chat Applications)
- Video Interaction
- Voice
- Web Platform (Our CPaaS Web Pages like 8x8 Connect, 8x8 Converse etc.)
- External Connectivity (Our connections to respective Countries and Operators grouped into Regions)
- Other
2. Incidents

In the Incidents sections, you will see Ongoing or Past Incidents which have respective severity. You may refer to the colour of the incident title with the below.

For each incident, we will be posting each stage of the incident from Investigating up until it is Resolved

For Incident of Partial and Major Outage, we will be posting a detailed Postmortem Report.

What is your DLR (Delivery Receipts) format for outbound SMS?

Delivery Receipts (DLR or DR) are Webhooks for delivery statuses: POST requests sent by 8x8 platform in JSON format to the delivery reports callback URL configured for your account.

Whenever a message has a new delivery status associated with the delivery stage it is in, 8x8 sends out a POST request with the new status to the callback URL.

DLR Webhook Format

Request body description

Parameter name	Parameter type	Description
namespace	string	A generic namespace for incoming webhook. Equal to `SMS` for delivery receipts.
eventType	string	Webhook type. Equals to `outbound_message_status_changed` for delivery receipts.
description	string	Human-readable description of the incoming event
payload	object	Delivery receipt information, see below.

Payload object description

Parameter name	Parameter type	Description
umid	uuid	A unique identifier generated by 8x8 for the message
batchId	uuid	A unique identifier generated by 8x8 for the message if sent using Batch API
clientMessageId	string	Your custom identifier for the message
clientBatchId	string	Client managed id for this batch of messages : your own unique reference
subAccountId	string	The sub-account id used to deliver the message
source	string	The source (i.e: sender) used to deliver the message
destination	string	Destination phone number where the SMS was sent (E.164 format)
status	object	Current status of the message, please see Message status reference for details.
price	object	Price information of the message, please see Price object reference for details
smsCount	integer	Number of SMS segment in the message

Below is a sample delivery receipt (DLR) for outbound SMS

{

"namespace": "SMS",

"eventType": "outbound_message_status_changed",

"description": "SMS outbound message delivery receipt",

"payload": {

"umid": "9e09ac86-bd74-5465-851d-1eb5a5fdbb9a",

"batchId": "3e09ac86-bd74-5465-851d-1eb5a5fdbb9b",

"clientMessageId": "1e09ac86-bd74-5465-851d-1eb5a5fdbb9b",

"clientBatchId": "2e09ac86-bd74-5465-851d-1eb5a5fdbb9b",

"subAccountId": "SubAccount-1",

"source": "8x8",

"destination": "+12025550293",

"status": {

"state": "undelivered",

"detail": "rejected_by_operator",

"timestamp": "2016-01-01T00:00:00Z",

"errorCode": 15, "errorMessage": "Invalid destination"

"price": {

"total": 0.0375,

"perSms": 0.0125,

"currency": "USD"

"smsCount": 3

}

For more information regarding DLR please look into our developer site via the below link:

https://developer.8x8.com/connect/reference/delivery-receipts-for-outbound-sms

SMPP bind - What is 8x8 SMS Throughput?

SMS throughput is the measure of data transfer between the connections measured by message per second.

At 8x8 CPaaS, our SMS throughput is tailored to each customer’s requirement during our onboarding process. This is to ensure our capacity are fully aligned with your business needs.

In most cases, for each bind connected to 8x8 SMPP servers, you will be able to submit a maximum of 50 messages per second. If you are not aware of your existing SMS throughput, you can check with your account manager about specific requirements.

For more information regarding SMPP connection, please refer to the below link.

https://developer.8x8.com/connect/reference/smpp-connection
What are the different message statuses ?
Here are the possible message statuses in 8x8 Connect:
- PROCESSING or RECEIVED - the message has been received by our platform and it is currently being processed before being sent to the carrier.
- SENT - The message has been sent to the operator and 8x8 has not received an acknowledgment yet from the operator.
- DELIVERED - This means the message has been "delivered to the handset". If the status is not available from the operators, this means that 8x8 has received the confirmation from the carrier that the message has been "delivered to the carrier".
- READ - This means the message has been read by the recipient
- UNDELIVERED - We have received confirmation that the message was not delivered. This can be due to various reasons such as:
- REJECTED - The message has not been accepted by our platform. This can be due to some errors such as incorrect mobile numbers or insufficient credit. You will not be charged for rejected messages.
What are the supported browsers for customer portal (8x8 Connect)?
Our customer portal (8x8 Connect) supports major browsers like Google Chrome, Safari, Microsoft Edge, and Firefox. For best experience please use Google Chrome.

Overview

Technical Specifications by Connection Type

1. For HTTP API Customers

2. For SMPP Customers

Required Actions

Step 1: Technical Review

Step 2: Protocol Upgrade & Re-routing

Step 3: Validation

Frequently Asked Questions (FAQ)

Support and Assistance

Subscribe to Updates

Subscribe to Components

1. Service Availability

2. Incidents