Email your customers, without another tool.
For software companies with news to share: a changelog, a newsletter, a launch. Send it from your own domain, and let people leave in one click.
From your list to their inbox.
The same account and the same domains as the rest of your mail.
- maya@example.com
- plan: pro
- jo@lumen.dev
- plan: free
- Plan
- is pro
- Country
- is Canada
- Match
- all of these
- From
- news@acme.dev
- List
- Pro customers
- Subject
- What's new in November
- Message
- We shipped three things this month. Here's what changed for you.
- Sent
- 4,083
- Delivered
- 4,021
- Opened
- 1,866
- Clicked
- 412
- Bounced
- 19
- State
- Sending, 5,000 an hour
The rules of good list mail, handled.
These are on for every campaign. There's nothing to set up.
Unsubscribes
Every campaign email carries the one-click header big mail providers ask bulk senders for.
People can pick the topics they want on a hosted page, linked from each email.
A send with no unsubscribe link gets one added.
Opening the link shows a confirm page. It keeps working years later.
Reputation
Every send checks it. Bounces and complaints go on it by themselves and can't be lifted.
A campaign with too many bounces or complaints stops before it hurts your domain, and says why.
Campaigns go out from a domain you verified.
Each copy goes to one person, with their own unsubscribe link.
Contacts
Plans count emails, not people.
Product news, the newsletter, event invites. Each starts opted in or opted out.
Filter on name, email, date added or any field you imported.
Find who opted in, who opted out and who never did.
What's where.
The dashboard covers the everyday send. The API and SDKs cover the rest.
In the dashboard
- Your contacts, with CSV import
- Who opted in and who opted out
- Send to everyone subscribed, or a saved segment
- A plain-text message, with unsubscribe added
Through the API
- Topics and saved segments
- Saved templates, HTML and merge fields
- A test run before sending
- Schedule and pace
- Pause, resume and stop
- Results: sent, delivered, opened, clicked, bounced
A campaign in four calls.
For when you want more than the dashboard's form, or want your own app to send it.
POST /v1/campaigns
{
"name": "November update",
"fromEmail": "news@acme.com",
"templateId": "…",
"segmentId": "…",
"throttlePerHour": 5000
}POST /v1/campaigns/:id/dry-run
# nothing is sent
# 200 { "recipientCount": 4120, "excludedCount": 37, "sample": [ … ] }POST /v1/campaigns/:id/send # now, or at its scheduledAt
POST /v1/campaigns/:id/pause
POST /v1/campaigns/:id/resume
POST /v1/campaigns/:id/abortGET /v1/campaigns/:id/metrics
# 200 { "totalRecipients": 4120, "sentCount": 4083,
# "failedCount": 0, "suppressedCount": 37,
# "events": { "delivery": 4021, "open": 1866, "click": 412, "bounce": 19 } }Before you start.
People who asked
You may only send to people who opted in. Purchased, rented or scraped lists aren't allowed.No automations
A campaign goes out when you send it. There are no sequences, automated journeys, A/B tests or drag-and-drop builder.Agents can't launch it
An agent's key can't start a campaign, even with full access. That takes a person in the dashboard or an app's full-access key.Plan and limits
Sending takes a Marketing plan and a verified domain. In its first 7 days, a workspace's send reaches up to 200 people.
Send your next update from Drin.
Start free and bring your list. Sending a campaign takes a Marketing plan.