12,270
edits
SMS API: Difference between revisions
m
no edit summary
m (→HTTP) |
mNo edit summary |
||
| (6 intermediate revisions by the same user not shown) | |||
|
==Inbound==
[[File:InboundSMS.png|none|frame|Inbound SMS option on Control Pages]]
===Email===
You may specify an email address and we'll send the messages by email.
===HTTP===
If you put an entry starting http:// or https:// then we will attempt to send the
The fields posted are as follows, but additional fields may be added from time to time.
The response text starts with either ERR: and an error message or OK:
example:
https://your.domain/yourscript.ext
We will then post or get using the field names as above.
==Outbound messages==
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.
===Response===
The response text starts either ERR: and an error message or OK:
You can choose to have a response back in XML - this makes the service more compatible with Acrobits' Groundwire mobile phone app that is a softphone with SMS capability. Add &xml to the URL.
===Example===
Example, using curl on linux:
| |||