Skip to main content
Version: 13.x (Current)

SMS Service Usage

This sections illustrates how to use the SMS Service.

POST /send

With this API you can send a new SMS.


According to GDPR, personal and sensitive information shall not be shared via SMS.


The body of the request should have the fields listed in the following table.

senderYesMessage sender. Twilio supports phone numbers in E.164 format or an alphanumeric ID, Kaleyra requires a registered sender ID.
receiverYesThe recipient phone number in E.164 format.
bodyYesThe text of the SMS you want to send.

By default, Kaleyra will create a Sender ID during the signup. However, using this default ID, you can only send SMS messages to your registered mobile number and the numbers that are added to the Team. Hence, you must create your own Sender ID to send an SMS to other mobile numbers.


The body of a single SMS can be up to 1600 characters long. If it's longer, the service will send the message as a segmented SMS and your account will be charged accordingly.

Here's an example of a valid request body:

"sender": "+15017122661",
"receiver": "+15558675310",
"body": "Your SMS body"



If something goes wrong during the request, the response will have a 4xx or 5xx status code and the following payload:

"statusCode": "400",
"error": "Bad request",
"message": "Exception description"

A notable status code is 429, which means that you have reached the REST API concurrency limit of Twilio (more information here).


In case of successful response with status code 200, the body of the response has the following structure:

"dateEvent": "2021-08-13T12:53:52.959Z",
"numSegments": "1",
"sid": "124354",
"status": "sent"
dateEventStringDate/time in ISO 8601 format when the message was delivered.
numSegmentsStringNumber of SMS messages it took to deliver the body of the message.
sidStringUnique identifier of the SMS.
statusStringMessage delivery status.