To send text SMS messages via the Esendex SMS API you use the SendService (XML Web Service (SOAP)) or the SendSMS (HTTP Form Post) services. These provide you with a range of methods and parameters to give you access to the range of SMS features Esendex provide.
The maximum number of characters supported is 160, without long messaging enabled, see Send Long SMS. The GSM Alphabet is a 7 bit alphabet with each character being described by one or two 7 bit values. The payload size on an SMS message is 140 bytes which gives space for in 160 x 7 bit values.Where a character requires two values to describe it, eg: €, this will reduce the actual number of characters supported. Any messages longer than 140 bytes will have characters truncated from the end are trunctated to fit within the 140 byte limit.
Dynamic Originator
This allows you to specify who the message appears to come from. This feature is primarily used to to brand messages with the senders company/service name. The following table gives details of the restrictions to consider when using this feature.
|
Length |
Reply Destination |
Trial Account |
Business SMS Account |
Premium SMS Account |
| Virtual Mobile Number |
15 digits |
Inbox |
- |
Supported |
- |
| Short Code |
4-8 digits |
Inbox |
- |
Supported |
Must match account short code |
| Alphanumeric |
11 characters |
Not possible |
- |
Supported |
- |
| Other Phone Number |
15 digits |
Phone |
- |
Supported |
- |
Validity Period
The validity period parameter on the Send SMS API methods allows you to specify, in hours, the period for which the message is valid. This will then be used by the operator to assess how long to retry the message should the destination handset be unavailable. This should be treated as a guide to the operator and not a guarantee that the message won't be delivered after this period.
The default is 72 hours (3 days) which is used in you supply a value of either 0 or greater than 71.
Delivery Receipts
Delivery Receipts are provided as standard on all messages sent through the Esendex. Details on how to access this information is given in the #Message Status# section.
Delivery Receipts are subject to the destination operator supporting the feature correctly.
Multiple Recipients
If you have the same message to send to multiple recipients, the most efficient method is to use the appropriate method/service to do this, eg SendMessageMultipleRecipients on SendService in the XML Web Service (SOAP). This allows EMS to use batch processing and submission technology to more efficiently process the messages.
The recommended maximum is 1000 recipients.
Multiple Messages
If you have many messages to send simultaneously, the most efficient method is to use the appropriate method/service to do this, eg SendMessageBatch on SendService in the XML Web Service (SOAP). This allows EMS to use batch processing and submission technology to more efficiently process the messages.
The recommended maximum number of messages in a batch is 100.