SMS API

This page contains technical details and as such may be quite long and hard to follow. If you cannot find the details you require please feel free to contact support who can explain things for you. You will also find many other customers on irc who can help with queries. Feel free to send us feedback if you think there are any errors in this page.

Overview

You can send SMS's using our web form or our simple 'API'.

You can use these systems to send an outgoing SMS, eg to a friend's mobile on another network. You can also use it to send a SMS to a SIP2SIM mobile device.

You can also control how incoming SMSs to your number or SIM are handled. For example, an incoming SMS to you can be sent onwards to your own HTTPS script.

Inbound

HTTP

If you put an entry starting http:// or https:// then we will attempt to send the text to you using HTTP (or HTTPS). If the URL ends with a ? or & then an HTTP GET is done with a set of form fields (i.e. name=value) containing information about the text. If the URL does not, then an HTTP POST is done using URL encoded form data.

The fields posted are as follows, but additional fields may be added from time to time.

Inbound SMS API Fields

username	This is the phone number as shown on the control pages for your VoIP number in full international format with no spaces.
password	The corresponding outgoing password for the username as set in the control pages for your VoIP number.
da	This is the number to which the message is to be sent and should be a full international format number (however, national format is also accepted). This may be a SIP2SIM ICCID to send direct to a SIM.
ud	This is the message to send, encoded in UTF-8.
limit	Set this to limit the number of parts that the message may be sent in.
costcentre	Optional, up to 10 characters, code that is included in the bill XML data.
private	Marks the message as private, see below
oa	Sets the sending number (see below). Normally not needed as your username is used.
udh	Hex UDH header, see below.
srr	Email address or URL for delivery report, see below

You will note that we have tried to use field names to match GSM 03.40 values. Other values may be included. For legacy reasons you can prefix the URL specified with a * to also send the older field names of timestamp, originator, destination, message.

We support UTF-8 coding of the full GSM 7 bit character set (including £$¥èéùìòÇØøÅåΔ_ΦΓΛΩΠΨΣΘΞÆæÉÄÖÑܧäöñüà€¡¿). Whilst one message is normally up to 160 characters some characters are coded using two characters using an ESC prefix in the 7 bit alphabet (€,[,\,],^,{,|,},~). The message will be coded as 7, 8 or 16 bit depending on what you include in the text, and this will impact the number of message parts that may be sent. If you include the invalid UTF-8 sequence 0xC0 0x80, then that includes a null in the message. If you include any unicode characters beyond U+0xFFFF then UTF-16 coding is used and sending of text in is UCS2 format. Not all interconnects or devices understand UTF-16 format.

The response text starts either ERR: and an error message or OK:

Example, using curl on linux:

curl --silent --get \
--form-string username=01234567890 \
--form-string password=123456 \
--form-string da=01234567890 \
--form-string ud="Hello world" \
https://sms.aa.net.uk/sms.cgi

Example with a simple URL:

 https://sms.aa.net.uk/sms.cgi?username=%2B441234567890&password=123456&da=%2B441234567890&ud=Hello+World

Outbound messages

We operate an outbound text service that is available to all of our customers that have a VoIP number. To use this service you must have an outgoing password configured in the control pages for the VoIP number.

To send texts you need to issue an HTTP GET or POST to our outbound text gateway https://sms.aa.net.uk/sms.cgi with the following fields as if sent from a form. As the password is sent in plain text you may prefer to use https.

OUtbound SMS API Fields

username	This is the phone number as shown on the control pages for your VoIP number in full international format with no spaces.
password	The corresponding outgoing password for the username as set in the control pages for your VoIP number.
da	This is the number to which the message is to be sent and should be a full international format number (however, national format is also accepted). This may be a SIP2SIM ICCID to send direct to a SIM.
ud	This is the message to send, encoded in UTF-8.
limit	Set this to limit the number of parts that the message may be sent in.
costcentre	Optional, up to 10 characters, code that is included in the bill XML data.
private	Marks the message as private, see below
oa	Sets the sending number (see below). Normally not needed as your username is used.
udh	Hex UDH header, see UDH messages.
srr	Email address or URL for delivery report, see below

Note that we have, again, tried to use GSM 03.40 field names, but alternative field names are supported for now: destination, originator, message.

We support UTF-8 coding of the full GSM 7 bit character set (including £$¥èéùìòÇØøÅåΔ_ΦΓΛΩΠΨΣΘΞÆæÉÄÖÑܧäöñüà€¡¿). Whilst one message is normally up to 160 characters some characters are coded using two characters using an ESC prefix in the 7 bit alphabet (€,[,\,],^,{,|,},~). The message will be coded as 7, 8 or 16 bit depending on what you include in the text, and this will impact the number of message parts that may be sent. If you include the invalid UTF-8 sequence 0xC0 0x80, then that includes a null in the message. If you include any unicode characters beyond U+0xFFFF then UTF-16 coding is used and sending of text in is UCS2 format. Not all interconnects or devices understand UTF-16 format.

The response text starts either ERR: and an error message or OK:

Example, using curl on linux:

curl --silent --get --form-string username=01234567890 --form-string password=123456 --form-string da=01234567890 --form-string ud="Hello world" https://sms.aa.net.uk/sms.cgi

Messages are charged per message part, see our main website for prices.

Delivery reports

In some cases we can provide a delivery report and indicate progress of a message. However this is not always possible and should not be relied on.

To use this, specify the srr either as an email address or a URL. The URL can include (typically after the ?) a string %code which will be replaced with a number that indicates progress. 1=Delivered, 2=Rejected, 4=Buffered, 8=Accepted by SMSC, and 16=Rejected by SMSC. Other % strings can be used such as %da or %dest as the original destination number, %oa for originator, %ud for the message.