...
Is there a single method that lets me choose the delivery channel (email/SMS)?
No, each channnel channel has its own endpoint and request format.
...
- in case you need only the basic feature, getting started with SMTP+ is usually easier because there are a lot of "ready to use" code snippets that help you implement a an SMTP client
- with APIs you can choose between providing the whole HTML code of the message or to refer an existing email template that may be personalized with merge tags. The The SMTP relay does not support templates instead.
- the way you access them is different. Parameters that are specified with message headers in SMTP+, in the API are handled as fields of a JSON object that is passed to the web services. For more details about these parameters please check out the examples that are provided for SMTP+
- with APIs you can take advantage of a set of additional methods for creating and retieving users
...
Which methods have to be used for sending transactional messages?
| Channel | Methods | Reference | Main request parameters | Optional request parameters | Returned values | ||
|---|---|---|---|---|---|---|---|
| Transactional Emails using APIs | Recipient's address, subject, email bodyscheduled datetime, campaign code*, ... | Error codes | ||||
| SMS |
| Transactional SMS using APIs
| Recipient's number, SMS textscheduled datetime, campaign code*, ... | Delivery ID |
*the campaign code is an ID that MailUp
Which are the main request parameters?
Here is a short list. Please refer to the API documentation for all the details.
| Main request parameters | Main options | Advanced options |
|---|---|---|
|
| |
| SMS |
|
|
*the campaign code is an ID that MailUp uses to group the mailing results by the specified ID.
For each new ID, MailUp creates a "message" object, which will act as result container
...