- your backend creates a short-lived popup session for one domain;
- your frontend opens the popup with one line of JavaScript;
- the restaurant sees the DNS records (copy or CSV), sets them in one click when its DNS provider supports it (Cloudflare, GoDaddy and others), and watches the check happen live;
- your page receives events such as
domain.verified.
The popup has a neutral look with a small “Powered by Minimo” line that you can turn off. It is in English and Italian.
Before you start
- An API key with the Domains permission (
domains), kept on your server. See Authentication. - The origins of the pages that will open the popup, set once. It is the same list as
allowedOriginsin the widget settings: if you already saved it there, skip this call. Each of the two calls reads and replaces that one list.
frame-ancestors), receive its events and be used as returnUrl. Exact scheme://host[:port] values: https only, http for localhost. No wildcards, at most 20. GET on the same path reads the list.
1. Create a session (your backend)
Response:
url is single use: it can be opened once (a reload of the same tab keeps working). To open the popup again, create a new session. Pass only the url to your frontend.
If the call fails: 400 INVALID_PARAMETERS with a userMessage (no allowed origin yet, or returnUrl not on an
allowed origin), 409 (the domain belongs to another workspace), 429 (more than 120 sessions in an hour).
Reference: Create Domain Popup Session.
2. Open the popup (your frontend)
Minimo.openDomainConnect returns { close() }. In popup mode call it from a click handler (browsers block popups opened later); if you fetch the session first, open the window synchronously and let the SDK reuse it, or use modal.
3. Events
Every event is apostMessage to your page, sent only to your allowed origins. The SDK checks the sender origin for you and calls onEvent({ type, sessionId, tenant, data }).
Without the SDK, listen yourself and check the origin:
GET /public/v1/domains/{id} or POST /public/v1/domains/{id}/verify.
What the user sees
- The DNS records to publish (ownership TXT, DKIM CNAMEs, DMARC, bounce MX and SPF), each with a copy button, plus Download CSV for whoever manages their DNS.
- Configure automatically when the domain’s DNS provider supports Domain Connect: the provider opens in its own window, the user approves, and control comes back to the popup, which checks again.
- Live verification: the popup checks every 15 seconds and on demand, with a status per record.
- Domain verified once the domain can send. The default sender (
info@for transactional,hello@for marketing) is created at that moment.
bounce.<domain> (MX and SPF) make its emails more trusted by mailboxes.
Security
- The API key stays on your server; the browser only gets a short-lived, single-use link.
- The link token and the popup’s session token are stored hashed. A replayed link reads as “already opened”.
- A session can only read and verify its own domain in your workspace.
- Embedding, events and
returnUrlare limited to your allowed origins. - Session creation and popup calls are rate limited.
If something fails
The domain stayspending until the records are found. failed means the records were missing for about 72 hours:
fix them and check again with Verify Domain. Every error code:
Errors and limits.