> ## 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. # Send One-Shot HTML Email > Dispatch a single transactional email by sending a pre-rendered HTML payload — no template required ## Overview Use this endpoint when you want to send a transactional email **without creating a template** in the dashboard. You provide the rendered HTML yourself and Minimo handles dispatch, delivery, and tracking. Typical use cases: * **Server-side rendered receipts**: invoices, order confirmations, shipping notifications * **Authentication flows**: magic links, OTP delivery, email verification * **Internal notifications**: alerts produced by your own background jobs * **Anything dynamic enough to not fit a pre-defined template** Tracking (open pixel + click rewriting) is injected **server-side**. Send your raw HTML as-is — don't pre-rewrite links or append a pixel yourself. ## Before You Start 1. Generate an API key with the **`TRANSACTIONAL`** permission from the Minimo dashboard. 2. Make sure your company's email provider is configured (SMTP or SES). 3. Have your HTML body ready — Minimo doesn't render templates for this endpoint. ## What the Server Does to Your HTML When you send `html`, the backend: 1. **Resolves placeholders**: `{{UNSUBSCRIBE_URL}}`, `{{PREFERENCES_URL}}`, and `{{FAKE_IMAGE_URL}}` are replaced with the per-recipient tracked URLs. 2. **Strips any pre-existing tracking pixel**: an `` whose `src` matches the Minimo open-pixel pattern is removed so it can't double-fire. 3. **Rewrites tracked anchors**: every `` pointing to `http(s)` or a relative URL is replaced with a click-tracking URL. `mailto:`, fragment-only (`#…`), and pre-existing `/api/click/*` links are left alone. 4. **Appends the open-tracking pixel** at the end of `` (or at the document root if no `` exists). The recipient receives the final HTML; analytics flow into `GET /public/v1/emails/{id}/stats`. ## Example Request ```bash theme={null} curl --request POST \ --url https://api.minimo.it/public/v1/emails \ --header 'Authorization: Bearer mn-{apiClientId}-{secret}' \ --header 'Content-Type: application/json' \ --data '{ "to": "customer@example.com", "subject": "Your receipt", "html": "

" }' ``` ## Response Shape The endpoint **always returns HTTP 200** when authentication succeeds — inspect `status` to know whether the provider accepted the message. ```json theme={null} { "data": { "id": "DMPNEF8", "status": "sent", "messageId": "0100019c8b3d4a4f-...", "statsUrl": "/public/v1/emails/DMPNEF8/stats" } } ``` When the provider rejects the message you still get back the same `id`, so the delivery row remains queryable: ```json theme={null} { "data": { "id": "DMPNEF8", "status": "failed", "failureReason": "Email address is not verified.", "statsUrl": "/public/v1/emails/DMPNEF8/stats" } } ``` ## Use Cases Render the receipt server-side and post it raw — Minimo rewrites the `View receipt` anchor into a tracked link. ```json theme={null} { "to": "customer@example.com", "subject": "Receipt for ORD-12345", "html": "

Thanks, Jane!

Your order ORD-12345 is on the way.

Track your order

" } ``` Override the sender per request to brand the email for a specific product surface. ```json theme={null} { "to": "newuser@example.com", "subject": "Sign in to Acme", "html": "

Hi! Click here to sign in. Link expires in 15 minutes.

", "fromAddress": "no-reply@acme.com", "fromName": "Acme Sign-In" } ``` Plain HTML with a single CTA is enough — the open and click events surface in the stats endpoint. ```json theme={null} { "to": "ops@example.com", "subject": "[ALERT] Queue depth above threshold", "html": "

Worker queue at 12,400 jobs.

Open dashboard

", "text": "Worker queue at 12,400 jobs. Open dashboard: https://admin.example.com/jobs" } ``` ## Best Practices ### Pair every send with a `statsUrl` lookup The response includes `statsUrl`. Persist the `id` (or the full `statsUrl`) alongside whatever business object triggered the send (order id, user id, etc.) so you can correlate opens and clicks later. ### Handle the `failed` branch `status: "failed"` means the provider rejected the message — usually a malformed recipient, an unverified sender, or a hard bounce. Surface `failureReason` to your operators, then either retry with corrected data or log the failure. ### Keep HTML self-contained Inline your CSS. Many email clients drop `