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

# Protections and sending limits

> How Minimo keeps one restaurant's bad list from hurting the others: daily limits for new restaurants, clean lists, automatic pause, optional review of the first campaigns

One restaurant that emails an old or bought list gets complaints and bounces that can hurt every restaurant's
delivery. These protections stop that restaurant early, **alone**, before it affects the others.

They touch only a restaurant's **marketing** emails (campaigns, review requests, offers, any marketing template sent
with a `tenant`). Booking confirmations, reminders and other service emails, sign-in emails and sends without a
`tenant` are never limited or paused.

> [!NOTE]
>
> Separate from these protections, a **new workspace** sends at most 100 emails a day in total, booking confirmations
> included, until its first credit top-up in **Settings → Plan & billing** (`402 QUOTA_EXCEEDED` over it). One top-up
> removes it for good.

## Example: check a restaurant

```bash theme={null}
curl https://api.minimo.it/public/v1/tenants/restaurant_4812/reputation \
  -H "Authorization: Bearer YOUR_MINIMO_KEY"
```

```json theme={null}
{
  "data": {
    "tenant": "restaurant_4812",
    "windowDays": 7,
    "marketingSent": 0,
    "complaints": 0,
    "hardBounces": 0,
    "hold": { "held": false, "since": null, "reason": null, "setBy": null },
    "workspaceHold": { "held": false },
    "rampUp": { "tier": "new", "dailyCap": 200, "usedToday": 0, "remainingToday": 200, "firstSeenAt": "2026-11-08T08:17:26.939Z" }
  }
}
```

`hold` says whether the restaurant's marketing is paused. `rampUp` is today's limit of a new restaurant. Permission
**Widgets** or **Events**. The full answer (rates, thresholds): [Get Tenant Reputation](https://docs.minimo.it/api-reference/embedded/tenants/get-reputation.md).
Only the pause: [Get Marketing Hold](https://docs.minimo.it/api-reference/embedded/tenants/get-marketing-hold.md).

## Daily limits for new restaurants

| Phase | When | Promotional emails per day |
| - | - | - |
| New | The restaurant's first 7 days | 200 |
| Warming up | Until day 30, or longer while its complaints or bounces are high | 1,000 |
| Established | After 30 days with clean numbers | No tenant limit |

* Days are UTC days. The phase starts the first time Minimo sees the restaurant (its profile, a session or a send).
* Over the limit, a send answers `422 TENANT_DAILY_CAP_REACHED` with `dailyCap`, `usedToday`, `remainingToday` and `tier`, and nothing is queued. An automatic marketing email due at that moment is skipped with `tenant_daily_cap_reached`. Never silently.
* A large campaign (over 300 recipients) of a new or warming-up restaurant goes out in waves over a few hours.
* The restaurant sees it in plain words in the [Statistics widget](https://docs.minimo.it/embedded/widget-statistics.md), under **Sending limited**: "You are in the start-up phase: you can send up to 200 promotional emails a day, 40 sent today. The limit grows by itself over time. Automatic messages have no limit."

## Optional review of the first campaigns

The checks on this page (daily limits, clean lists, list quality, automatic pause) are always on. On top of them, a workspace that sends for restaurants has **one more setting**: the first **3** campaigns of every restaurant can wait for a person at Minimo before they go out. It is a setting of your workspace, on by default, and it is not one of the automatic checks.

* You can ask Minimo to switch it off for your workspace. At **0**, no campaign waits for a manual review and every campaign goes out with the automatic checks only. Today Minimo changes this setting for you: there is no API key permission or screen for it.
* While it is on, a send of one of the restaurant's first 3 campaigns answers `status: "in_review"` and the [Campaigns widget](https://docs.minimo.it/embedded/widget-campaigns.md) shows "Campaign under review" with the pill **In review**.
* Approved: the campaign is queued at once, nothing else to do. Rejected: it shows **Not approved** and does not count; the restaurant creates a new one, which is reviewed again.
* From the fourth campaign on, campaigns go out with the normal checks.

## Clean lists

A restaurant's list is people who booked or signed up with it. Addresses that look like an old or bought list never enter it:

| Address | Example | Added in a widget | `POST /public/v1/tenants/{tenant}/subscriptions` item |
| - | - | - | - |
| not valid, or a typo of a big provider | `mario@gmial.com` | `422 TENANT_CONTACT_INVALID_EMAIL` | `outcome: invalid`, `code: invalid_email` |
| throwaway mailbox | `x@mailinator.com` | `422 TENANT_CONTACT_DISPOSABLE_EMAIL` | `code: disposable_email` |
| generic mailbox | `info@`, `noreply@`, `support@` | `422 TENANT_CONTACT_ROLE_EMAIL` | `code: role_email` |

Nothing is saved for a refused address. Withdrawals (`status: unsubscribed`) are never refused. Booking events are not filtered: a confirmation always goes out.

When a restaurant sends a campaign, before anything is queued:

* not valid, throwaway, generic and already bounced or complained addresses are **skipped**; the answer then carries `listQuality: { total, skipped }` and the widget says how many were skipped;
* if more than **20%** of a list of 20 or more addresses would be skipped, the whole campaign is refused with `422 TENANT_LIST_QUALITY`;
* if nobody is left, `422 NO_VALID_RECIPIENTS`; if nobody left has given consent, `409 CAMPAIGN_NO_ELIGIBLE_RECIPIENTS`.

The widgets show every refusal in the restaurant's language.

## Automatic pause

Minimo checks each restaurant's last 7 days every few minutes, and between the waves of a running campaign. A restaurant's marketing is **paused** when:

| Trigger | Line |
| - | - |
| Spam complaints over its marketing sends | Above 0.3%, with at least 100 marketing sends and at least 2 complaints |
| Complaints on one campaign | 2 or more |
| Hard bounces (address does not exist) over its sends | Above 5%, with at least 100 sends |

One complaint alone never pauses a restaurant. Your **whole workspace**'s campaigns are paused when 2 or more restaurants are paused, or when the workspace's complaint rate is above 0.3% (at least 200 sends and 2 complaints).

While a restaurant is paused:

* a campaign or a marketing send for it answers `409 MARKETING_SEND_ON_HOLD` (with `tenant` and a `userMessage` in English and Italian); a running campaign stops at its next wave;
* an automatic marketing email due for it is skipped with `tenant_on_hold`;
* its booking confirmations and reminders keep going out normally;
* the [Statistics widget](https://docs.minimo.it/embedded/widget-statistics.md) shows "Sending paused", without the reason or the numbers.

Minimo is alerted on every pause. Only Minimo can lift it: write to us with the restaurant's reference.

## What helps a restaurant stay clean

* Import only guests who booked or signed up with that restaurant, never purchased or very old lists.
* Record consent where it is given (the booking form) and send it with the event, see [consent](https://docs.minimo.it/embedded/consent.md).
* Let guests unsubscribe easily: the footer and the one-click header are always there, keep them.

## If something fails

The codes of this page (`TENANT_DAILY_CAP_REACHED`, `TENANT_LIST_QUALITY`, `NO_VALID_RECIPIENTS`,
`CAMPAIGN_NO_ELIGIBLE_RECIPIENTS`, `MARKETING_SEND_ON_HOLD`) are explained in
[Errors and limits](https://docs.minimo.it/embedded/errors.md#marketing-protections).

## Next step

[Go live](https://docs.minimo.it/embedded/go-live.md)


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