Skip to main content
Each restaurant sees the latest emails sent to its guests and what happened to each one. Your backend can read the same list.

Mount it

Permission history (in the default):
Events: ready with count, error, resize.

What the restaurant sees

Send history: the latest 100 emails sent to the restaurant’s guests, newest first, one row each: Only this restaurant’s emails appear: the sends you made with its tenant, the emails of its automatic rules and its campaigns. It is read-only. An automatic email that Minimo skipped before sending it (rule switched off, booking too close, no consent, bounced address) is not in this list. GET /public/v1/scheduled-sends lists it, with status: skipped and the reason.

The same data from your backend

Every message carries the tenant you sent it with. List one restaurant’s messages (permission transactional):
For totals and rates per restaurant use GET /public/v1/tenants/{tenant}/stats, see the Statistics widget. For the sends planned by the automatic rules use GET /public/v1/scheduled-sends, see Automatic messages.

If something fails

A missing email is often a skipped automatic send: GET /public/v1/scheduled-sends lists it with its reason. Every code, with what to do: Errors and limits.

Next step

Contacts widget