Last Update: 2024-03-21
There are 4 variants how to send a transactional SMS. Whether to use an existing SMS template or if the whole message text is provided, and whether to use an existing address record as recipient or a provides mobile number.
Info: If the text is longer than 160 characters, than it will be splitted into multiple SMS (which will be automatically concatened again by every mobile phone). There are only 153 characters per SMS if it gets splitted. These numbers are only valid if all characters are within the 7-Bit GSM 3.38 charset. Otherwise the messages gets encoding with 16-Bit Unicode, where the max length of one SMS is 70 characters. (see https://de.wikipedia.org/wiki/GSM_03.38)<?xml version="1.0" encoding="UTF-8"?> <smstrigger customerid=""> <id></id> <address key="Attribute12"></address> </smstrigger>
<?xml version="1.0" encoding="UTF-8"?> <smstrigger customerid=""> <id></id> <mobilenumber>43664...</mobilenumber> </smstrigger>
<?xml version="1.0" encoding="UTF-8"?> <smstrigger customerid=""> <message><![CDATA[...]]></message> <address key="Attribute12"></address> </smstrigger>
<?xml version="1.0" encoding="UTF-8"?>
<smstrigger customerid="">
<message><![CDATA[...]]></message>
<mobilenumber>43664...</mobilenumber>
</smstrigger>
| Element | Format | Description |
|---|---|---|
smstrigger | ||
↳ id | int | ID of SMS |
↳ message | int | Text of SMS |
↳ address | varchar | Recipient is an existing address |
↳ @key | varchar | Key-field by which the address is specified (default="Email") |
↳ mobilenumber | int | Recipient is given mobilenumber (with country prefix) |
On success the internal ID of the created job will be returned in response->data.