Transactional email
Send email from any app with no setup, or from your own domain.
Plans: Every plan, including the free app
| Email / day | Free app | Starter | Team | Business | Client business |
|---|---|---|---|---|---|
| Included | 10 | 25 | 50 | 500 | 50 |
What you get
- Send from any app with no setup
- Send from your own domain once it is verified
- HTML and plain text, with a reply-to address
- One message to one or several people
- Bounce and complaint tracking for each domain
- Daily sending shown against your plan
How it works
An app with email turned on sends a message with one request to the Whisk API. With no sender address, the mail goes from Whisk's shared address under the app's name. Nothing needs to be set up first.
To send from your own domain, an owner adds it under Settings, Email, and publishes the DNS records Whisk shows. Once they are verified, apps can send from any address on that domain. Mail from any other domain is refused with a message naming the domains that are verified.
Whisk sends through an established email delivery service and watches bounces and complaints for each domain. If they rise too high, sending from that domain is paused and the owner is told. It is for transactional mail, such as reminders, confirmations and failure alerts, not newsletters.
Example
An accounting practice emails each client a list of the documents still needed for their tax return. The email comes from the practice's own domain, and replies go straight to the client's account manager.
For your coding agent
email: true
The app then sends with a POST to /v1/orgs/<org>/apps/<app>/email/send using WHISK_SERVICE_TOKEN, with to, subject, html or text, and optionally from and reply_to. The request is described in the agent instructions.