Transactional email messages are also called triggered emails. Unlike bulk emails, they are sent one at the time on per need basis and contain highly personalized content.
Examples of triggered emails can be one-off messages, such as password reset, statement generated, etc.
We offer a simple REST- based API for sending messages and for getting reports.
Since our Transactional Email Service is one of our APIs, it conforms to the general API rules:
Our transactional email service is built around our email editor. Using the editor removes a lot of issues stemming from managing internal HTML code and saves you time and money:
Our Transactional Email Service gives you separation of responsibilities: everyone does what they do best at the time of their choosing!
Use our editor to design all of your transactional messages.
Our responsibilities are:
Check out the how to create and edit templates
The left image is a template, and the right one is a complete merged/sent message.
Just submit this JSON document to trigger sending a message.
1 2 3 4 5 6 7 8 9 10 11 12 |
|
See the API for sending a single message.
Sending Transactional emails requires that templates for these messages are created prior to sending. Such templates can have merge fields, in a format ${field_name}
. This feature allows a high degree of flexibility for message customization.
The template to be sent can have a number of merge fields, with data for merging dynamically provided during an API call.
You can start from scratch and start your first message in a couple of minutes. Follow this step by step tutorial to see how.
Transactional API is a subject to Rate limiting, like any other API.