Jump to content

This is the support site for Andrews & Arnold Ltd, a UK Internet provider. Information on these pages is generally for our customers but may be useful to others, enjoy!

SMS API: Difference between revisions

444 bytes removed ,  13 August 2020
m
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 with either ERR: and an error message or OK:
 
Example, using curl on linux:
<syntaxhighlight lang="bash">
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
</syntaxhighlight>
 
Example with a simple URL:
<syntaxhighlight lang="bash">
https://sms.aa.net.uk/sms.cgi?username=%2B441234567890&password=123456&da=%2B441234567890&ud=Hello+World
</syntaxhighlight>
 
==Outbound messages==
autoreview, Bureaucrats, editor, Interface administrators, reviewer, Administrators
12,270

edits