Skip to main content
Send an event each time a booking is created, changed or cancelled. The rules decide which emails go out and when.

Send events (your backend)

When the booking changes or is cancelled, send the same cancellationKey. In a booking.updated, send the full booking, not only what changed: its payload replaces the details of the pending emails.
The response (202) tells you what was planned:
Read tenantAutomations: it lists what was scheduled for the restaurant. The top-level status and automations are about a different feature (workspace automations started by an event) and can say no_automation even when emails were scheduled.

What happens at send time

Nothing decided when the event arrived is trusted when the email is due. Minimo checks again that the rule still exists and is on for the tenant, that the guest still exists and did not hard-bounce, that the template is there, that the sender is still allowed and, for a marketing template such as the review request, that the guest has marketing consent and the workspace is not on a marketing hold. The unsubscribe footer and List-Unsubscribe header apply as for every send. A send that does not go out is never an error to you: it is recorded with a reason.

If something fails

A date without its UTC offset answers 422 INVALID_EVENT_DATE. A wrong tenant or field answers 400 INVALID_PARAMETERS. A send that does not go out is not an error: read its reason in GET /public/v1/scheduled-sends. Every code: Errors and limits. Reference: Send Event.

Next step

Schedule one email yourself, if your backend already knows when an email must go out.