Support – 8x8 CPaaS Help Center

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.

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 (supported by certain Chat Apps channels only)
UNDELIVERED - We have received confirmation that the message was not delivered. This can be due to various reasons such as:

Mobile handset is unavailable (e.g. mobile is switched off or on roaming mode)
Filtered out by the operator

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.