Character support
When specifying the message body in the request, the characters used as well as the length of the message affect how many actual SMS messages are sent out. When using parameterization, the length of each message may also vary depending on the recipient-specific data.
Individual characters used in the message determine the type of encoding that will ultimately be used to send the SMS message. The API automatically detects the encoding required from the characters used, which allows us to support the delivery of SMS in any language.
Auto Encoding
Send fewer message parts by condensing Unicode characters. Learn more here.
Contact your account manager to turn on this feature.
Basic character set
You can send up to 160 characters in a single SMS message if all characters in your message are part of the GSM 7-bit character set:
GSM 7 bit default alphabet and extension table
3GPP TS 23.038 / GSM 03.38
x0 | x1 | x2 | x3 | x4 | x5 | x6 | x7 | x8 | x9 | xA | xB | xC | xD | xE | xF | |
0x | @ | £ | $ | ¥ | è | é | ù | ì | ò | Ç | LF | Ø | ø | CR | Å | å |
1x | Δ | _ | Φ | Γ | Λ | Ω | Π | Ψ | Σ | Θ | Ξ | ESC | Æ | æ | ß | É |
2x | SP | ! | “ | # | ¤ | % | & | ‘ | ( | ) | * | + | , | . | / | |
3x | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | : | ; | < | = | > | ? |
4x | ¡ | A | B | C | D | E | F | G | H | I | J | K | L | M | N | O |
5x | P | Q | R | S | T | U | V | W | X | Y | Z | Ä | Ö | Ñ | Ü | § |
6x | ¿ | a | b | c | d | e | f | g | h | i | j | k | l | m | n | o |
7x | p | q | r | s | t | u | v | w | x | y | z | ä | ö | ñ | ü | à |
1B 0x | FF | |||||||||||||||
1B 1x | ^ | |||||||||||||||
1B 2x | { | } | \ | |||||||||||||
1B 3x | [ | ~ | ] | |||||||||||||
1B 4x | ||||||||||||||||
1B 5x | ||||||||||||||||
1B 6x | € | |||||||||||||||
1B 7x |
LF
is the Line Feed character - for JSON format, provide it as \n
SP
is the Space character
Extended Character Set
The following characters are also available, but they're counted as two characters in the SMS message rather than one:
|
, ^
, €
, {
, }
, [
, ]
, ~
, \
Other Characters
If other characters are required for different languages, 16-bit Unicode (UCS-2) encoding will be used. When using UCS-2 encoding, each character will take 2 bytes, which means up to 70 characters can be sent per UCS-2 encoded SMS message.
Long Messages
The message body in a request can contain a maximum of 2000 characters. However, 7-bit encoded messages allow up to 160 characters in one single message. Unicode encoding allows for up to 70 characters in a single message. And the header of each message takes up a few characters. So how can we accomplish up to 2000 characters? We use multiple messages that, in most cases, reassemble on the user's device. To your customers, it looks like one long message. You can use the charts below to determine how many actual SMS messages your text contains.
Note that messages longer than 2000 characters will result in a 400 error.
Using only 7-bit Characters
Each SMS in a multi-part 7-bit encoded message has a maximum length of 153 characters.
Message Length | Number of SMS Parts |
---|---|
1–160 | 1 |
161–306 | 2 |
307–459 | 3 |
460–612 | 4 |
613–765 | 5 |
766–918 | 6 |
919–1061 | 7 |
1062–1214 | 8 |
1215–1367 | 9 |
1368–1520 | 10 |
1521–1673 | 11 |
1674–1826 | 12 |
1827–1979 | 13 |
1980–2000 | 14 |
Using Unicode Characters
Each SMS in a multi-part Unicode encoded message has a maximum length of 67 characters.
Note:
On the Sinch Customer Dashboard, the Encoding field of Unicode encoded messages is set to UCS2.
Message Length | Number of SMS Parts |
---|---|
1–70 | 1 |
71–134 | 2 |
135–201 | 3 |
202–268 | 4 |
269–335 | 5 |
336–402 | 6 |
403–469 | 7 |
470–538 | 8 |
539–605 | 9 |
606–672 | 10 |
673–739 | 11 |
740–796 | 12 |
797–853 | 13 |
854–924 | 14 |
925–991 | 15 |
992–1058 | 16 |
1059–1115 | 17 |
1116–1182 | 18 |
1183–1249 | 19 |
1250–1316 | 20 |
1317–1383 | 21 |
1384–1450 | 22 |
1451–1517 | 23 |
1518–1584 | 24 |
1585–1651 | 25 |
1652–1781 | 26 |
1782–1848 | 27 |
1849–1915 | 28 |
1916–1982 | 29 |
1983–2000 | 30 |