12,270
edits
SMS API: Difference between revisions
m
no edit summary
(Created page with "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 e...") |
mNo edit summary |
||
|
The fields posted are as follows, but additional fields may be added from time to time.
{| class="wikitable"
|+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.
| 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
| |||