- Transactional messages (email or SMS) can be issued using the following API method: POST /api/transactional/send
- Typical scenarios for transactional emails are welcome emails upon registering or a receipt following a purchase transaction.
- To be noted that welcome emails don't have to be API coded, as Ongage offers an automatic built-in welcome email feature, that can be setup from the List Settings Page (see there help section on "How to Setup a List Welcome Email").
- Each List comes with 1 default transactional campaign already setup, but you can add additional campaigns for different types of transactional emails with the following method:
POST api/transactional which is used to create a new transactional mailing campaign.
- If you don't indicate a mailing_id when calling the transactional mailing method, then all mailing stats and data will get associated with the default transactional campaign for that list.
- By default when issuing a call to send a transactional message, the contact's status (unsub, bounce, complant status) is ignored, that's in order to accommodate sending receipts regardless if the contact is unsubscribed or not (similarly suppression lists are also ignored). The Transactional method does have flags to indicate whether to take into account the status and/or suppression list . See details about the check_status flag and check_global_and_list_suppression flag under the API method: POST /api/transactional/send
- When issuing a Transactional message you can either indicate the Email/SMS Message ID or Send HTML/Text Content in the body of API Call. In the latter case you will need to encode the HTML code passed in the body of the call by using some function like: json_encode($html-email); (See example here: POST /api/notify_transactions).