Bulk SMS API - Email to SMS

You can use our Email API to send SMS text messages to one, or hundreds, of recipients at once. The email API is simple to use, quick to setup and compatible with almost any application, script or programming language that can generate an email with a specific to, subject and message body.

Sending Emails to the SMS gateway

You can use any of the following e-mail formats. Each one been designed to meet a common need and offers different facilities. This gives you the option to choose an API that best fits your requirements.

Format Description
Simple Email Input API Just send an email to <phone_number>@itsarrived.net and the subject and body of the email becomes the text message that is sent to <phone_number>.
Format 1 API This is most useful for sending different messages to different users in one email.
Format 2 API This is ideal for sending the same message to many users or where you need advanced options like delayed delivery.
Format 3 API Similar to Format2, but with the ability to send non-textual content such as Nokia OTA picture messages, operator logos and RTTTL ringtones.
Designed to send multimedia, but also plain text, messages. Ideal for sending a message and an image together, for example.

Email formats:

Simple Email Input API (Email-to-Text)
Just send an email to <phone_number>@itsarrived.net and the subject and body of the email becomes the text message that is sent to <phone_number>.
Format 1 API
This is most useful for sending different messages to different users in one email.
Format 2 API
This is ideal for sending the same message to many users or where you need advanced options like delayed delivery.
Format 3 API
Similar to Format2, but with the ability to send non-textual content such as Nokia OTA picture messages, operator logos and RTTTL ringtones.
Designed to send multimedia, but also plain text, messages. Ideal for sending a message and an image together, for example.

Email Authentication

We check every email that you send to our Format1,2,3,4 APIs to make sure that it contains the correct valid Username and PIN for your account.

As well as your Username and PIN we also check the e-mail to make sure that it came from the usual PC that you use to send massages. The first time you send us an e-mail containing SMS messages, we profile the email and extract some "fingerprint" information that helps us identify your particular system. We then check all subsequent e-mails against this profile before accepting them. As a result you must send all emails from one particular PC or system. Should you decide to change or upgrade the PC, let us know and we will clear the profile until your next email arrives. This is done to reduce the chance of fraudulent use of your account.

Plain Text Format Emails

The emails you send to our SMS gateway must be plain-text format. Our Email-to-SMS APIs do not support HTML formatted emails at this time.

Character Sets

Our SMS gateway will send the first 160 characters of the text message (as defined by the API below). If the text message contains any characters that are not part of the default , such as international character sets, the message is limited to 70 unicode characters. Any characters over this limit will be truncated.

Email Templates

If you are using Outlook to compose the emails for sending SMS or MMS messages using our API's then you can significantly speed up the process by creating a template for the email message and assigning it to a toolbar icon. The whole process takes less than ten minutes to set-up and will save you a lot of time and effort. See the page for more details.

Simple Email Input API (Email-to-Text)

With Simple Email Input (Email-to-Text) you just send an email to <recipient>@itsarrived.net and the subject plus body of the email with be delivered as a text message to <recipient> . This makes it particularly easy to send an SMS message from applications such as Outlook or Outlook Express and is ideal for small offices that need a simple way to add text messaging facilities for staff, for example.

The recipient can be one of the following:

  • A mobile/cell phone number in full international format, including the country and area code. For example 447700912345@itsarrived.net for a UK mobile.
  • An Contacts Manager Name (to send to all entries in the Contacts Manager). For example another.12345@itsarrived.net.
  • An Contacts Manager Group: specify the Contacts Manager Name, followed by two colons and the Group name. You'll need to put this in inverted commas, for example "another.12345::group1"@itsarrived.net.

In order to use the service you must first register those email addresses that you wish to permit to send messages using your account. You can do that on the Email-to-Text Configuration page. Anyone sending an email from the email addresses you register will be able to send an SMS message which will be charged to your account.

Note that it is very easy to "spoof" email messages and anyone can, potentially, send SMS messages and charge them to your account if you decide to use this facility.

If a person with registered email address another@somecompany.com wants to send an SMS message to +447700912345

Simple email input example

When this is received by the server a plain text SMS message will be sent to the handset whose number is 447700912345 containing the text:

"Call the office Please call Mary on 01234567 as she needs to know when you will be back."

Email Format 1 API

This is useful for sending different messages to different users in the same email.

The To: is your account <Username>@itsarrived.net. For example ANOther.61234@itsarrived.net .

The subject line of the e-mail must contain either the single word format1 , or the two words format1 noreply (separated by a space) if you do not want an email confirmation .

The body contains your PIN, the messages and their recipients in the following format:


Identifier=<PIN>
|<recipient1>|<message1>|
|<recipient2>|<message2>|
|<recipientN>|<messageN>|

For example:

Email format1 example

The first line must contain the tag Identifier= immediately followed by your PIN and a newline.

The second and subsequent lines are a list of recipients and the messages you want to send. You must have three pipe characters "|" in each line, as shown, to delimit the different values.

Each recipient can be one of the following:

  • A mobile/cell phone number in full international format, including the country and area code. For example 447700912345 for a UK mobile.
  • An Contacts Manager Name (to send to all entries in the Contacts Manager). For example another.12345.
  • An Contacts Manager Group: specify the Contacts Manager Name, followed by two colons and the Group name. For example another.12345::group1.

You must not have a blank line in the middle of the recipient/message list. List processing stops at any blank line so as to ignore any "signature" at the end of the message. It's a good idea to leave a blank line after the last telephone number/message - this makes the end of the list unambiguous.

Setting the Originator Address (Sender ID)

If you want to set the Originator Address this can be done on the 2nd line (ReplyTo):

Identifier=12345678
ReplyTo=MyCompany
|447700912345|Call the office urgently|
			

Email Format 2 API

This is useful for sending the same message to many users. Format 2 also offers the ability to set the delayed delivery.

The To: is your account <Username>@itsarrived.net. For example ANOther.61234@itsarrived.net .

The subject line of the e-mail must contain either the single word format2 or the two words format2 noreply (separated by a space) if you do not want to receive an email confirmation.

The body contains your PIN, message and the recipients:

To: <Username>@itsarrived.net
Subject: format2
                
PIN=<PIN>
ReplyTo=<MyCompany>
SendTimeDelay=<1...10080>
SendTimeAbsolute=<YYYY-MM-DDTHH:MM:SS>
Message=<message>

<recipient1>
<recipient2>
<recipientN>

For example:

Email format2 example

The first line must contain the text PIN= immediately followed by your PIN and a newline.

If you wish to set the Originator Address then you can, optionally, use the tag ReplyTo.

If you wish to delay a message then you can, optionally, use the tag SendTimeDelay OR the tag SendTimeAbsolute

SendTimeDelay is followed by a number indicating the number of minutes that the message should be delayed. The value must be between 1 minute and 10080 minutes (7 days) for example SendTimeDelay=30 will delay the message for 30 minutes.

SendTimeAbsolute is followed by the date and time in the future when you want the message sent. This can be in UTC (GMT) or can specify the offset from UTC and has a maximum delay of 7 days. The general format is SendTimeAbsolute=YYYY-MM-DDTHH:MM:SS±HH:MM for example

SendTimeAbsolute=2003-12-25T07:30:00
SendTimeAbsolute=2003-12-25T07:30:00-05:00

The first example will send the messages on 25 December 2003 at 07:30 GMT. The second example will send the message on 25 December 2003 at 07:30 local time where local time is 5 hours earlier than GMT.

The next line must start Message= is followed by your message which may be split over multiple lines. It will be truncated at 160 characters.

Newlines / carriage returns are normally filtered out. If you need these in your message you can add them by inserting a line in your message that only contains the '@' character. For example:

Message=This is the first line of the message.
@
This is the second line of the message.

You must leave at least one blank line after the message and then list the recipients, one per line. Each recipient can be one of the following:

  • A mobile/cell phone number in full international format, including the country and area code. For example 447700912345 for a UK mobile.
  • An Contacts Manager Name (to send to all entries in the Contacts Manager). For example another.12345.
  • An Contacts Manager Group: specify the Contacts Manager Name, followed by two colons and the Group name. For example another.12345::group1.

You must not have a blank line in the middle of the recipient list. List processing stops at any blank line so as to ignore any "signatures" at the end of the message. It's a good idea to leave a blank line after the last recipient - this makes the end of the number list unambiguous.

Each e-mail message can contain one, hundreds or thousands of recipients.

Email Format 3 API

This is useful for sending picture messages, operator logos and ringtones.

The subject line of the e-mail must contain either the single word format3 , or the two words format3 noreply (separated by a space) if you do not want an email confirmation . The content of the body of the e-mail depends on whether you wish to send Text, a Picture Message, Group Graphic, Operator Logo or Ringtone.

The structure consists of four blocks:

  1. Block #1- PIN line which may also have additional option to set the ReplyTo values
  2. Block #2 - a line defining the message type e.g. Message=, GroupGraphic=, OperatorLogo= or Ringtone=
  3. Block #3 - a line, or lines, that define a recipient and the parameters associated with that recipient. The SendTo tag must be the last tag in each block.
  4. Block #4 - End

Each recipient can be one of the following:

  • A mobile/cell phone number in full international format, including the country and area code. For example 447700912345 for a UK mobile.
  • An Contacts Manager Name (to send to all entries in the Contacts Manager). For example another.12345.
  • An Contacts Manager Group: specify the Contacts Manager Name, followed by two colons and the Group name. For example another.12345::group1.

Block #3 can be repeated multiple times to send the Message, Group Graphic, Operator Logo or Ringtone to multiple recipients.

MCC & MNC codes can be found on our SMS text messaging coverage tables.

Here are some examples

Format 3 for a Text Message

Email format3 textmessage example

Format 3 for a Picture Message

Email format3 picture message example

Format 3 for a Group Graphic

Email format3 group graphic example

Format 3 for a Operator Logo

Email format3 operator logo example

Format 3 for a Ringtone from the library

Email format3 library ringtone example

Format 3 for a Ringtone from an RTTTL or RTX string

Email format3 ringtone example

Confirmation/Acknowledgment

How do I know if the messages were processed?

When we process an email message from you using any of the email API's we will send a reply to you with details of how we handled each message (unless you specify noreply in the subject line). If all the messages were processed successfully you will get an email like this:

This is an automated response to your e-mail submission of 1
text message sent to It's Arrived at Wed, 31 Oct 2001 11:00:18 -0000.

All of your messages have been processed.

You can view the delivery status of the messages by logging onto the website
http://www.csoft.co.uk/extranet.

Do not hesitate to ask for help if you require it.

If any of your messages were not processed successfully you will receive an e-mail like this:

This is an automated response to your e-mail submission of 1
text message sent to It's Arrived at Wed, 31 Oct 2001 11:07:08-0000.

One of your messages has not been processed and is shown below. Do not hesitate to ask for help if you require it.

Report #185 - Insufficient Credit to Send Message
The messages below were not sent because you ran out of credit.
Please cut and paste them into an e-mail and send them to <Username>@itsarrived.net
after you have purchased more credit.

---------- Cut below here ----------
PIN=123456789
Message=testing format 2

07700912345
---------- Cut above here ----------

What does "Report Code 38 - Wrong PIN" mean?

Each PIN is associated with a particular email sending program and email user. Each email that arrives is checked to see that it is coming from the usual email program (such as Outlook) and user (such as "Ade Oyeniyi"). If you have multiple users on different computers then each of them needs to use a different PIN. Just make a support request for a new PIN and one will be sent to you free of charge.

Your session is about to expire

You will be logged out in seconds.

Do you want to stay signed in?

Yes, keep me signed in     No, Sign me out