Automatic messages widget

​

What the restaurant sees

• My automatic messages: one row per transactional template you listed in masterTemplateIds (booking confirmation, reminder, review request…), marked Standard or Personalized.
• Preview shows the email as the restaurant’s guests will get it, with the restaurant’s brand. Merge fields such as {GUEST_NAME} stay visible.
• Personalize creates the restaurant’s own copy of the template and opens it in the Minimo email editor, in the same frame. Edit reopens a copy; Reset to standard deletes the copy and goes back to your version.
• Automatic sends (shown when you defined rules): when each message goes out (“Immediately”, “1 day before”), with an On / Off switch. Off stops that send for this restaurant only.

​

Mount it

<div id="minimo-templates"></div>
<script src="https://api.minimo.it/public/v1/embed/widgets/widgets.js"></script>
<script>
  Minimo.mountWidget({
    url: session.urls.templates,
    container: '#minimo-templates',
    minHeight: 760,
    onEvent: function (event) {
      if (event.type === 'template.saved') console.log('copy saved', event.data.templateId);
      if (event.type === 'automation.toggled') console.log(event.data.rule, event.data.enabled);
    },
  });
</script>

​

The editor

• remove the footer with the unsubscribe link, or hide the sender identity line;
• replace the email with HTML that drops the unsubscribe link (422 TENANT_FOOTER_REQUIRED);
• change merge variables: they stay as they are and are filled at send time.

​

Sending with the restaurant’s version

curl -X POST https://api.minimo.it/public/v1/templates/email/send \
  -H "Authorization: Bearer YOUR_MINIMO_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "transactional": "TRF4MS9",
    "recipient": "guest@example.com",
    "tenant": "restaurant_4812",
    "customFields": { "GUEST_NAME": "Anna", "BOOKING_TIME": "20:30" }
  }'

• transactional is the template uid (7 characters).
• POST /public/v1/transactionals behaves the same way. Add sendAt to schedule the email.
• If you send the id of a restaurant’s copy directly, the message is still recorded for its tenant; a tenant that does not own that copy answers 422 TENANT_TEMPLATE_MISMATCH.
• Brand values you leave out of customFields (RESTAURANT_NAME, LOGO_URL, BRAND_COLOR…) come from the tenant profile.

​

Your templates as masters

• List them in masterTemplateIds of PUT /public/v1/widgets/settings. Transactional templates show here; campaign templates are the starters of the Campaigns widget.
• Confirmations, reminders and cancellations are utility (service) emails. A review request, an offer or a newsletter is marketing: a utility template that reads like one is refused as a master (422 MASTER_LOOKS_PROMOTIONAL). See consent.

​

Events