Receipts and confirmations are the emails customers open most. Send them from your backend through the Send API with the same interactive blocks as your campaigns, so every receipt can ask how the order went and offer the next product.
A receipt reaches nearly every customer, right after they've bought. That makes it the best place for a quick rating, a refill or a code for next time, as long as it's as easy to send as a plain one.
Design it once, send it from your backend
Build the receipt as a normal email in the studio, with merge tags such as {{order_number}} and the blocks you want:
- Rating: "How was your order?" on stars or emoji faces. With Ask a follow-up when rating is at most, a low score opens a short question about what went wrong.
- Product: a related item or a refill, bought from the receipt with Buy now.
- Coupon: a code for the next order, copied with a tap.
- Button: order status, invoice or support.
Then your backend calls POST /api/v1/send with the email's projectId and a mergeData object holding that order's values, up to 100 fields. See Template in the API reference.
Every customer can rate, buy and click from the receipt, whatever app they read it in.
Linked to your contacts
When the customer is already one of your contacts, the receipt is linked to them: pass a listId, or let MailInApp find the address in your lists. Their rating then lands on their activity and engagement score, can fill a contact field and start a journey, and a booking block books in one click.
Built for production
type: "transactional", the default, reaches customers who unsubscribed from marketing, since they still need their receipt. Addresses that bounced are skipped. See Transactional vs. marketing.Idempotency-Key: a retried call with the same key returns the first result, so each customer gets one receipt. See Idempotency.- Limits: each API key has a per-minute limit, and your plan includes a monthly number of Send API calls. Recent calls are listed on the Developers page.
- No code: the Send Transactional Email action in Zapier and the n8n node send the same way.
- A one-time code: send
htmlortextinstead of aprojectId, and the message goes out exactly as given.
What comes back
Ratings, clicks and purchases show up in the email's Insights like any campaign's, and your webhook posts each one to your systems as it arrives. A low-score alert tells you when a customer rates an order poorly, so someone can reach out the same day.
Getting started
Build the receipt in the studio with a Rating, mint an API key under Developers, and call POST /api/v1/send with your projectId and mergeData. The quickstart walks through the first call.