Emails

Sixty-seven messages, all in your colours.

Sign-up, order, appointment, abandoned cart, test result: every moment has its email. Their body is an ordinary page, built with the same editor as the rest of the site.

  1. Sixty-seven events covered
  2. Body written in the page editor
  3. Subject and body both accept variables
  4. Each event states which variables it provides
  1. Sender and reply-to address per email
  2. A log of every send
  3. Essential emails cannot be switched off
  4. Scheduled follow-ups

How it is set

An email that has gone out cannot be called back. So the API refuses an unknown token, and will not let you switch off the emails without which a customer would lose their account or their proof of purchase.

Read an event's contract before writing

GET /api/agent/v1/emails/evenements/

{ "code": "order_confirmation",
"libelle": "Order confirmation",
"obligatoire": true,
"raison_obligatoire":
"This email is the customer's proof of purchase.",
"cles": {
"commande_numero": "Order number",
"commande_total": "Total incl. VAT",
"prenom": "Recipient's first name"
} }

Dress the email

PATCH /api/agent/v1/emails/12/
{
"sujet": "Your order [%commande_numero%]",
"page": 94
}
→ a token the event does not provide is
REFUSED: it would reach the customer as raw text