Editor, Interface administrators, Administrators
19
edits
SMS API: Difference between revisions
→Inbound
|
You list one or more ''targets'' for your SMS, separated by a space.
We work out what type of target from the format.
The targets can also be prefixed by a special character to impact the format of how the message is sent. These are currently +, *, or !. (This is an issue for an email address that starts with one of these, but for email the * prefix does nothing, so in the rare case of an email starting with *, !, or +, prefix with a *)
===Email===
You may specify an email address, e.g. ''localpart''@''hostname'' and we'll send the messages by email.
*The prefix format + may be used to force mobile numbers
===Toot===
You may specify a fediverse address, e.g. @''name''@''hostname'' to get messages as a toot (''direct mention'').
*The prefix format + may be used to force mobile numbers
===Mobile===
You will note that we have tried to use field names to match GSM 03.40 values. Other values may be included.
*The prefix format * may be used to also send the older field names of ''timestamp'', ''originator'', ''destination'', ''message'', but we recommend updating your scripts to use the new field names.
We support UTF-8 coding of the full GSM 7 bit character set (including £$¥èéùìòÇØøÅåΔ_ΦΓΛΩΠΨΣΘΞÆæÉÄÖÑܧäöñüà€¡¿) and from UCS16 messages and UTF-16 surrogates. Not all of our SMS interconnects handle all of the coding, so we send the message as best we can.
| |||