Skip to main content

​
Overview

Embedded Minimo is for a SaaS that wants to give its own customers email (booking confirmations, reminders, review requests, campaigns) without building an email platform. The example used across these pages is a restaurant management app: the SaaS is the app, each restaurant is a customer, each restaurant’s guests receive the emails.
  • One Minimo workspace for your whole SaaS. You sign up once. Your restaurants never get a Minimo account and never see the Minimo dashboard.
  • Each customer is a tenant. A tenant is just a string you choose (your restaurant id, e.g. restaurant_4812). You pass it on every call; Minimo keeps each tenant’s templates, contacts, consent, sends and statistics apart.
  • Your customers work inside your product. Minimo hosts ready-made screens (widgets) that you embed with one line of JavaScript, in your look, in English or Italian.
  • Your backend sends events, Minimo does the rest. Booking created, moved, cancelled: Minimo sends the right email at the right time from the restaurant’s own domain, and cancels what is no longer needed.

​
Who does what

​
What a restaurant gets

Plus two things that need no widget: guests unsubscribe on pages that show the restaurant’s name and logo (consent), and every restaurant can send from its own domain or from a subdomain of yours (domain connect, senders).

​
The pieces

First widget in 15 minutes

Settings, a session from your backend, one iframe in your page.

Widget sessions and events

Session fields, permissions, embedding, events, security.

Automatic messages

Rules, booking events, sendAt, cancellation.

Consent and unsubscribe

Marketing vs service emails, consent per workspace or per restaurant.

Protections and sending limits

Daily limits for new restaurants, first campaigns reviewed, automatic pause.

Domains and senders

Each restaurant sends from its own domain, or from a subdomain of yours.

Go-live checklist and FAQ

What to set up before the first real restaurant.

​
API keys and permissions

Every call from your backend uses one Minimo API key (Authorization: Bearer mn-…), kept on your server. The embedded endpoints use these permissions:
The permission list in Developer → API keys does not offer widgets yet. Ask Minimo for a key with exactly the permissions above (recommended). A key created with no permission selected can call every endpoint: if you use one, keep it on your server like any secret.

​
Language and look

  • The widgets, the unsubscribe pages and the domain popup are in English and Italian (the locale you pass).
  • The widget pages have a neutral look and a small “Email by Minimo” line at the bottom. Pass poweredBy: false and they carry no Minimo name.
  • The emails your restaurants send never carry a Minimo badge.

​
What is coming

WhatsApp from the restaurant’s own number. Today the WhatsApp widget connects a restaurant’s number and shows its state, and Minimo turns the connect button on per workspace. Sending booking messages and replies from that number is the next step. Until then, automatic messages and campaigns are email.