> ## Documentation Index
> Fetch the complete documentation index at: https://docs.minimo.it/llms.txt
> Use this file to discover all available pages before exploring further.

# Go live

> The checklist before your first real restaurant, and short answers to the questions teams ask most

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](https://docs.minimo.it/embedded/quickstart.md).
* 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**](https://app.minimo.it/settings/domain)
  of the dashboard, with **every** record Minimo lists published (including the two `bounce.` records). See [Senders and domains](https://docs.minimo.it/embedded/senders-and-sending.md).
* 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](https://docs.minimo.it/embedded/domain-connect.md)) 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](https://docs.minimo.it/embedded/start-here.md#which-way-to-send)), 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](https://docs.minimo.it/embedded/automations.md)): 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](https://docs.minimo.it/embedded/widget-brand.md#tenant-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](https://docs.minimo.it/embedded/consent.md): 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](https://docs.minimo.it/embedded/protections.md).
* 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](mailto:info@minimo.it) before the first campaign.
* Marketing emails reach only guests who agreed. Booking emails always go out.

## FAQ

> [accordion] Do my restaurants need a Minimo account?
>
> No. They work inside your app through the widgets. Only your app has a Minimo workspace.

> [accordion] Can a restaurant see another restaurant’s data?
>
> No. Every widget session belongs to one restaurant: the templates, guests, sends and statistics of the others
> answer `404`.

> [accordion] Do the emails show the Minimo brand?
>
> Never. Only the widget pages show a small "Email by Minimo" line, removed with `poweredBy: false`.

> [accordion] My backend sent the same event twice. What happens?
>
> The second one has the same `idempotencyKey` and answers `"status": "duplicate"`: nothing is sent twice.

> [accordion] The booking moved or was cancelled. What do I send?
>
> `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.

> [accordion] How do I know a restaurant switched off a message?
>
> Your page gets `automation.toggled` from the widget, and `GET /public/v1/tenants/{tenant}/automations` returns the
> rules in force for that restaurant.

> [accordion] How do I bill my restaurants?
>
> Every email carries its `tenant`. List them with `GET /public/v1/messages/list?tenant=…`, or read totals with
> `GET /public/v1/tenants/{tenant}/stats`.

> [accordion] Which languages?
>
> 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](https://docs.minimo.it/embedded/consent.md#the-pages-guests-see)).

> [accordion] And WhatsApp?
>
> Coming soon. Today automatic messages and campaigns are email only.

## Next step

You are ready for your first real restaurant. Keep [Errors and limits](https://docs.minimo.it/embedded/errors.md) at hand.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.