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

# Schedule one email yourself

> Send one email at a set time with sendAt, check it, cancel it or move it, without rules

If your backend already knows when an email must go out, you can skip the rules and schedule a single send with
`sendAt`.

## Schedule an email

Add `sendAt` to `POST /public/v1/transactionals` or `POST /public/v1/templates/email/send` (scope `transactional`):

```bash theme={null}
curl -X POST https://api.minimo.it/public/v1/transactionals \
  -H "Authorization: Bearer YOUR_MINIMO_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "transactional": "TRF4MS9",
    "recipient": "guest@example.com",
    "tenant": "restaurant_4812",
    "sendAt": "2026-11-19T20:30:00+01:00",
    "idempotencyKey": "booking-4812-reminder",
    "cancellationKey": "booking-4812",
    "customFields": { "GUEST_NAME": "Anna", "BOOKING_TIME": "20:30" }
  }'
```

The answer is HTTP `201` with `status: 202` inside (scheduled, not sent):

```json theme={null}
{
  "data": {
    "status": 202,
    "sent": 0,
    "scheduled": {
      "id": 1042, "status": "pending", "sendAt": "2026-11-19T19:30:00.000Z", "recipient": "guest@example.com",
      "transactional": "TRF4MS9", "tenant": "restaurant_4812", "cancellationKey": "booking-4812",
      "idempotencyKey": "booking-4812-reminder", "duplicate": false
    }
  }
}
```

* `transactional`: the template uid (7 characters). Send the master: the tenant's copy is picked when the email goes out.
* `sendAt`: ISO 8601 **with its UTC offset**, in the future, at most 90 days ahead (`422 INVALID_SEND_AT` otherwise, with a `userMessage` that says what is wrong). Without `sendAt` nothing changes: the email goes now and the response is the usual one.
* Checked now: the template exists, `tenant`, `replyTo`, the sender (`from`/`senderId` under a verified domain). Checked again when it goes out, like any send: the tenant's version of the template (picked at that moment), the sender, bounces, marketing consent (marketing templates only: a utility email is never blocked by consent) and the tenant's sending limits.
* `idempotencyKey`: the same key again returns the send already scheduled (`duplicate: true`), nothing new is planned. On `/templates/email/send` it is a UUID.
* Goes out **once**, at most a minute late; more than 5 minutes late (e.g. an outage) it is skipped, never sent late.
* Never for sign-in, verification or system emails and never with a one-time code or sign-in link in the fields (`422 SEND_AT_NOT_ALLOWED`). On `/templates/email/send` it schedules the template content: no `html`, `subject`, `text` or `attachments`.

```bash theme={null}
# Status of one scheduled send, or the list (filters: tenant, cancellationKey, status)
GET    /public/v1/transactionals/scheduled/1042
GET    /public/v1/transactionals/scheduled?tenant=restaurant_4812&cancellationKey=booking-4812
# Cancel one (only while pending; once sending or sent: 409 SCHEDULED_SEND_NOT_CANCELLABLE;
# an already cancelled one answers 200 with its row)
DELETE /public/v1/transactionals/scheduled/1042
# Cancel everything still pending for a booking of one tenant -> { "data": { "cancelled": 1 } }
DELETE /public/v1/transactionals/scheduled?cancellationKey=booking-4812&tenant=restaurant_4812
```

Send the `DELETE` calls without a body and without a `Content-Type: application/json` header (an empty JSON body is refused with `400`).

These sends are separate from the rules: a `booking.cancelled` event does not cancel them and `/public/v1/scheduled-sends` does not list them.

## Move a scheduled email

There is no "move" call. Cancel the email, then schedule it again with the new `sendAt` and a **new**
`idempotencyKey` (the old key still points to the cancelled email, so reusing it returns that one):

```bash theme={null}
# 1. Cancel the pending reminder of booking 4812
curl -X DELETE "https://api.minimo.it/public/v1/transactionals/scheduled?cancellationKey=booking-4812&tenant=restaurant_4812" \
  -H "Authorization: Bearer YOUR_MINIMO_KEY"

# 2. Schedule it again at the new time
curl -X POST https://api.minimo.it/public/v1/transactionals \
  -H "Authorization: Bearer YOUR_MINIMO_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "transactional": "TRF4MS9",
    "recipient": "guest@example.com",
    "tenant": "restaurant_4812",
    "sendAt": "2026-11-21T20:30:00+01:00",
    "idempotencyKey": "booking-4812-reminder-2",
    "cancellationKey": "booking-4812",
    "customFields": { "GUEST_NAME": "Anna", "BOOKING_TIME": "21:30" }
  }'
```

With the [rules](https://docs.minimo.it/embedded/automations.md) you do not need this: a `booking.updated` event moves the pending emails for
you.

## If something fails

`422 INVALID_SEND_AT` (no UTC offset, in the past, or more than 90 days ahead), `422 SEND_AT_NOT_ALLOWED` (sign-in or
one-time-code emails), `409 SCHEDULED_SEND_NOT_CANCELLABLE` (already sending or sent). Every code:
[Errors and limits](https://docs.minimo.it/embedded/errors.md#sending). Reference:
[Send Transactional Email](https://docs.minimo.it/api-reference/messaging-channels/email/send-transactional.md).

## Next step

[Senders and domains](https://docs.minimo.it/embedded/senders-and-sending.md)


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