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

# Contacts widget

> Each restaurant manages its own guests: search, add one or paste a list with consent, fix, remove, download as CSV

Each restaurant manages its own guests: search, add one or paste a list with consent, fix, remove, download as CSV.

## Mount it

Permission `contacts` (in the default). Mount `urls.contacts` from a [widget session](https://docs.minimo.it/embedded/widgets.md):

```html theme={null}
<div id="minimo-contacts"></div>
<script src="https://api.minimo.it/public/v1/embed/widgets/widgets.js"></script>
<script>
  Minimo.mountWidget({ url: session.urls.contacts, container: '#minimo-contacts', minHeight: 700 });
</script>
```

## What the restaurant sees

**My contacts**: the restaurant's own guests (every guest belongs to exactly one restaurant), 25 per page, with a search by name, email or phone and a filter (subscribed, unsubscribed, no consent, blocked). The restaurant can:

* **Add one contact** (email, first name, last name, phone) with a consent box and an optional "how they agreed".
* **Paste a list**: up to 200 lines, one contact per line as `email, first name, last name, phone` (comma, semicolon or tab). Each line gets an outcome: added, or skipped with a reason. With the consent box, the restaurant must write how the consent was collected.
* **Fix** first name, last name and phone of any of its contacts; the email only while no consent is on record (otherwise remove the contact and add the new address).
* **Remove** a contact from the restaurant and **download** its contacts as CSV.

There is no file upload. To bring in a restaurant's existing guests, the restaurant pastes them (200 lines at a time),
or your backend sends them with the [subscriptions API](https://docs.minimo.it/embedded/consent.md#subscriptions-api) (500 per call).

## Events

| `widget` | `type` | `data` |
| - | - | - |
| `contacts` | `ready` | `count` |
| `contacts` | `contact.added` | `contactId`, `outcome` (`added`), `consent`; for a pasted list `contactIds`, `count` |
| `contacts` | `contact.updated` | `contactId`, `changed` (fields) |
| `contacts` | `contact.removed` | `contactId` |
| `contacts` | `contacts.exported` | `count` |

## What stays as it is

* **One guest, one restaurant**: adding an address always creates or updates the guest of this restaurant. The answer is the same whether or not the address exists in your workspace or at another restaurant: nothing tells the restaurant who else has it, and no other restaurant's data is ever shown or changed.
* **Consent per restaurant** (see [consent](https://docs.minimo.it/embedded/consent.md#consent-per-restaurant)): the box records the guest's consent to this restaurant with its evidence (session, IP, browser, the restaurant's text). A guest who unsubscribed is never subscribed again from the widget.
* **Read only**: unsubscriptions and blocked addresses. A bounce shows (the address is dead for everyone); a spam complaint shows only when it was about this restaurant's own email; an unsubscription from every email sent through your SaaS shows as a plain unsubscription. "Receives campaigns" is the answer of the real campaign check.
* Contacts created here are **not** contacts of your workspace: they do not appear in your dashboard, do not start your workspace's own automations and do not get your workspace's marketing consent.
* **Remove** withdraws the guest's consent to this restaurant and moves the guest to the bin; its history stays. Adding the same address again brings it back.
* Limits per session: 30 changes per minute, 5 pasted lists and 10 exports every 10 minutes.
* **Clean lists**: an address that is not valid (including typos of big providers such as `gmial.com`), a throwaway mailbox or a generic one (`info@`, `noreply@`, `support@` and similar) is refused, when added one by one and on each pasted line (reasons `invalid_email`, `disposable_email`, `role_email`). See [clean lists](https://docs.minimo.it/embedded/protections.md#clean-lists).

## If something fails

The widget shows every refusal in the restaurant's language. The codes (`TENANT_CONTACT_EMAIL_LOCKED`, `TENANT_CONTACT_EMAIL_TAKEN`, `TENANT_CONTACT_PASTE_TOO_LARGE`, `TENANT_CONSENT_EVIDENCE_REQUIRED`, `INVALID_TENANT_CONTACT`, `TENANT_CONTACT_INVALID_EMAIL`, `TENANT_CONTACT_DISPOSABLE_EMAIL`, `TENANT_CONTACT_ROLE_EMAIL`, `429`) are in [Errors and limits](https://docs.minimo.it/embedded/errors.md#restaurants-and-guests).

## Next step

[Statistics widget](https://docs.minimo.it/embedded/widget-statistics.md)


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