Skip to main content
A restaurant’s marketing email reaches only its guests who agreed, with proof of that consent. This page shows how to record the consent and what guests see when they unsubscribe. Send it from your booking form, with what the guest saw and when they agreed:
Each guest gets an outcome in the answer. Reference: Record Guest Consent.

Two kinds of email

The category is set on the template. A review request is marketing. A service template that reads like a promotion cannot be an automatic message for restaurants (422 MASTER_LOOKS_PROMOTIONAL on PUT /public/v1/widgets/settings). Every restaurant has its own guests. The same address at another restaurant, or in your own workspace, is another contact. So a consent always belongs to one restaurant. There is nothing to switch on.
  • The subscriptions call above: PUT (or POST) /public/v1/tenants/{tenant}/subscriptions, permission Widgets or Events, up to 500 guests per call.
  • The booking event on POST /public/v1/events with tenant and marketingConsent: true. Put the details in payload.consentEvidence. See Rules.
  • The consent box in the Contacts and Campaigns widgets.
A consent for one restaurant never changes what the guest agreed with another one or with your workspace. marketingConsent: true on POST /public/v1/contacts with tenant is refused (422 TENANT_CONSENT_NEEDS_EVIDENCE): a consent without evidence would not count.

Subscriptions API

  • source: where the consent was collected: booking, api (the default) or import. Any other value answers 400 INVALID_PARAMETERS. To record the name of your form, use evidence.consentVersion.
  • Every evidence needs ref. An evidence without ref fails the whole call with 400 INVALID_PARAMETERS and nothing is saved.
  • outcome per guest: subscribed, unsubscribed, unchanged, skipped_opted_out (unsubscribed earlier, no newer consent), contact_not_found or invalid (with error, for example a subscription without evidence).
  • A guest new to the restaurant is created as its guest, with the consent and its evidence.
  • GET /public/v1/tenants/{tenant}/subscriptions?email=… returns one guest’s status, evidence and canReceiveMarketing. Reference: Get Guest Consent.

What Minimo checks when it sends

  • A marketing email goes only to a guest of that restaurant whose consent has its evidence. Everyone else is skipped, at send time and again when a scheduled email is due.
  • A single send to someone else is refused and nothing is sent: 422 MARKETING_CONSENT_REQUIRED (not a guest, or no consent) or 422 TENANT_SUBSCRIPTION_REQUIRED (the guest agreed, but without evidence). Record the consent first.
  • Every marketing email of a restaurant has the unsubscribe footer and the one-click List-Unsubscribe header.
  • In the editor a restaurant cannot remove the footer, hide the sender identity line or replace the email with HTML that drops the unsubscribe link (422 TENANT_FOOTER_REQUIRED).
  • The rules check consent again when a marketing email is due. A guest who unsubscribed meanwhile is skipped (no_marketing_consent).
  • Service emails are never blocked by consent.

Unsubscribes, complaints, bounces

  • The unsubscribe link and the mailbox unsubscribe button stop that restaurant only. The page names the restaurant, shows its data controller, and offers to stop every email sent through your SaaS (every restaurant and your workspace) for that address.
  • A guest who unsubscribed can be subscribed again only with a consent given later (evidence.consentedAt). The widgets never subscribe them again.
  • A spam complaint about a restaurant’s email stops that restaurant’s marketing to that guest and counts against the restaurant (see protections).
  • A bounce makes the address dead for everyone.

The pages guests see

The unsubscribe link of every email opens a page hosted by Minimo, in English or Italian. The language comes from the text of the email, not from the restaurant:
  • Minimo reads the subject and the text and looks for common words of a language (at least 3).
  • A short email, or one with few such words, gets an English footer and an English page. Write your Italian templates with full sentences.
  • Any language other than Italian gives an English page.
What the page shows:
  • The restaurant’s name, logo, color and data controller (from the tenant profile), never your SaaS’s branding.
  • A confirm button and an optional reason. The mailbox unsubscribe button (the List-Unsubscribe header) works without the page. There is no one-click “subscribe again” on the success page.
  • The preferences page shows that restaurant only: who can write to the guest, then the channels (Email, WhatsApp, SMS). Empty contact fields are hidden. These switches change nothing at other restaurants or in your workspace.
Nothing to build: set the restaurant’s name, logo and legal details in the tenant profile, or let the restaurant set them in the Brand widget.

If something fails

On a workspace without embedded widgets the subscriptions endpoints answer 409 TENANT_CONSENT_NOT_ENABLED: save the widget settings first, or use the contact’s marketingConsent and POST /public/v1/contacts/opt-out. Every other code: Errors and limits.

Next step

Protections and sending limits