Skip to main content
Minimo gives your customers email (booking confirmations, reminders, review requests, campaigns) without you building an email platform. The example in these pages is a restaurant-manager app: each restaurant is one of your customers, and each restaurant emails its guests. Words are defined in the glossary.
  • One workspace for your whole app. You sign up once. Your restaurants never get a Minimo account.
  • One tenant per restaurant. A string you choose, such as your restaurant id (restaurant_4812). Minimo keeps each restaurant’s templates, guests, consent, sends and statistics apart. The same address at two restaurants is two guests.
  • Restaurants work inside your app. Minimo widgets are ready-made screens you embed with one line of JavaScript, in English or Italian.
  • Your backend says what happened, Minimo sends. Send the email now, or send booking events and let Minimo send each email at the right time, and cancel it when the booking is cancelled.

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).

Guests and the contacts API

Save your widget settings first. Minimo keeps each restaurant’s guests apart only once your widget settings exist. Call PUT /public/v1/widgets/settings with at least allowedOrigins (see Embedded widgets). Do it before your first send, booking event or contact with tenant.Until then, tenant is only a label on the message. Each email address is one contact of your workspace, shared by all restaurants. Consent and protections per restaurant do not apply yet.
Your API key reaches every restaurant of your workspace. On the contacts API, tenant says which restaurant’s guest you mean: An update by id keeps the guest in its tenant: it never starts your workspace automations and its consent changes only with evidence (use the subscriptions API).

API keys and permissions

Every call from your backend uses one API key (Authorization: Bearer mn-…), kept on your server. You create it in Developer → API keys (Quickstart, step 1). The embedded endpoints use these permissions: The key form starts with Subscribe, Transactional, Stats, Webhook and Goals selected. Keep Transactional. Remove the others: the embedded pages do not need them. Open the list to add Widgets, Events and Domains. A permission cannot be added to a key later: create a new key. A key without the permission an endpoint needs gets 401 INVALID_TOKEN, the same answer as a wrong key.

Language and look

  • The widgets, the editor and the domain popup are in English and Italian only (the locale you pass). There is no Spanish or German version. A locale other than en or it is refused with 400 INVALID_PARAMETERS. Pass en or it for a restaurant that speaks another language.
  • The unsubscribe pages are in English or Italian too. A guest whose language is neither sees English.
  • The emails are in the language you write them in. Any language works.
  • The widget pages show a small “Email by Minimo” line. Pass poweredBy: false and they carry no Minimo name.
  • The emails your restaurants send never carry a Minimo badge.

Next step

Quickstart: send the first email for a restaurant Related: Start here · Go live · Errors and limits