Skip to main content
A transactional e-mail answers something a person did: an order confirmation, an invoice, a sign-in link, an appointment reminder. Unlike a campaign, it does not go to a list, depends on no marketing consent, and is not unsubscribed from. Lekalao sends them for your applications, and keeps them in a log with their opens, their clicks and any failures.

​
Three ways to send them

The API

A POST with the template’s name, the recipients and the variables.

Laravel transport

A Laravel application keeps Mail::to()->send(), Lekalao does the rest.

SMTP relay

Any application that speaks SMTP.

​
How it works

  1. You write a transactional template in the interface, with a name that does not move (order-confirmation).
  2. Your application calls it by that name with its variables.
  3. Lekalao renders it, logs it and answers at once. The e-mail then leaves from a queue of its own, through the transactional provider, with new attempts for up to six hours if the provider fails. See The answer.
You may also send complete HTML without a template, through the API or the transport.

​
And campaigns?

Use a separate provider (or at least a separate stream, like Postmark’s message streams) for transactional e-mail: a reputation problem on your campaigns will then not stop your invoices arriving. See A provider per kind of sending.