Skip to main content
Do these once, in this order. Each line links to the page with the details.

1. Your workspace

  • An API key with Widgets, Events and Transactional (and Domains if your app connects domains), kept only on your server. See Quickstart, step 1.
  • Widget settings saved before the first send, booking event or contact with tenant: PUT /public/v1/widgets/settings with the origins of your app (production, and staging if it shows the widgets). Until then Minimo does not keep restaurants apart.
  • One credit top-up in Settings → Plan & billing. Until then the workspace sends at most 100 emails a day, booking confirmations included (402 QUOTA_EXCEEDED over it).

2. Sending domain and senders

  • Your own domain verified once, for example yoursaas.example, in Settings → Domain of the dashboard, with every record Minimo lists published (including the two bounce. records). See Senders and domains.
  • Do it before any restaurant sends a campaign. Without a verified domain a campaign cannot be sent, and the Campaigns widget shows only INVALID_PARAMETERS.
  • Each restaurant sends from its own domain (domain popup) or, with no DNS work, from a subdomain of yours such as bookings@trattoriadamario.yoursaas.example.
  • A restaurant cannot send as its @gmail.com address (422 SENDER_NOT_ALLOWED). Send from your subdomain with the restaurant’s name.

3. Emails

Pick how you send (Start here), then:
  • Your HTML (POST /public/v1/emails): every email with tenant. Use it for service emails only.
  • Templates and events: master templates for confirmation, reminder and cancellation marked as service emails (utility in the editor); the review request, offers and newsletters marked marketing. Merge fields named the same in every template and in your events (GUEST_NAME, BOOKING_TIME, PARTY_SIZE…).
  • Template names: the restaurants see each master and each campaign starter by its name, as you wrote it. Use names they understand, such as “Booking confirmation”.
  • API keys from the dashboard: the first save of a template in the dashboard also creates an API key named Template — send from code. If you do not need these keys, delete them in Developer → API keys (row menu, Delete API). Templates created with your API key create no extra key.
  • Several languages: every restaurant sees every language version of your masters and rules in the Automatic messages widget. There is no filter by language.
  • Booking events (details): the same cancellationKey for every event of one booking, a new idempotencyKey for each event, every date with its UTC offset, and the full booking in every event (a booking.updated replaces the details of the pending emails).

4. Restaurants

  • A restaurant profile for each one (PUT /public/v1/tenants/{tenant}): name, logo, legal name, address, privacy link. The email footer and the unsubscribe page use it.
  • Consent: send marketingConsent with its evidence when a guest agrees to marketing. Without it, the guest gets service emails only.
  • Widgets: a new session each time the page opens, locale from the restaurant’s language, poweredBy: false if you want no Minimo name.

5. A full test with a test restaurant

  • A test tenant and test inboxes you own, never real guests. Throwaway mailbox domains (such as mailinator.com) are refused when added to a restaurant’s list.
  • Send a booking: the confirmation arrives from the right sender, with the restaurant’s name and logo.
  • Cancel it: the reminder is cancelled (GET /public/v1/scheduled-sends?cancellationKey=…).
  • Open the unsubscribe link: the page names the restaurant.
  • Open the history and statistics widgets for the test restaurant.

6. Tell your restaurants

  • New restaurants have a daily limit for marketing emails, bad lists are refused, and a restaurant with complaints is paused alone. Service emails are never limited by these protections.
  • The first 3 campaigns of each restaurant are reviewed by a person at Minimo before they go out. To turn this off for your workspace, write to info@minimo.it before the first campaign.
  • Marketing emails reach only guests who agreed. Booking emails always go out.

FAQ

No. They work inside your app through the widgets. Only your app has a Minimo workspace.
No. Every widget session belongs to one restaurant: the templates, guests, sends and statistics of the others answer 404.
Never. Only the widget pages show a small “Email by Minimo” line, removed with poweredBy: false.
The second one has the same idempotencyKey and answers "status": "duplicate": nothing is sent twice.
booking.updated with the full booking and the new date moves the pending reminder. booking.cancelled cancels everything still pending. Both with the same cancellationKey as the booking.
Your page gets automation.toggled from the widget, and GET /public/v1/tenants/{tenant}/automations returns the rules in force for that restaurant.
Every email carries its tenant. List them with GET /public/v1/messages/list?tenant=…, or read totals with GET /public/v1/tenants/{tenant}/stats.
English and Italian only for the widgets and the editor (the locale you pass). There is no Spanish or German version. The emails are in the language you write them in. Any language works. The unsubscribe page is Italian when the email text is Italian, otherwise English (see the pages guests see).
Coming soon. Today automatic messages and campaigns are email only.

Next step

You are ready for your first real restaurant. Keep Errors and limits at hand.