Send from your app in one call.
The API, the SDKs, SMTP and the command line all feed one queue, with the same retries, block list and signed webhooks.
curl -X POST https://api.drin.run/v1/emails \
-H "Authorization: Bearer $DRIN_API_KEY" \
-H "Idempotency-Key: order-1042-receipt" \
-H "Content-Type: application/json" \
-d '{
"from": { "email": "hello@acme.com", "name": "Acme" },
"to": [{ "email": "maya@example.com" }],
"subject": "Your receipt",
"html": "<p>Thanks for your order.</p>"
}'
# 202 { "id": "6f1c…", "status": "queued" }import { DrinClient } from "@drin00/sdk";
const drin = new DrinClient({ apiKey: process.env.DRIN_API_KEY! });
const { id, status } = await drin.emails.send(
{
from: { email: "hello@acme.com", name: "Acme" },
to: [{ email: "maya@example.com" }],
subject: "Your receipt",
html: "<p>Thanks for your order.</p>",
},
{ idempotencyKey: "order-1042-receipt" },
);import os
from drin import DrinClient
drin = DrinClient(api_key=os.environ["DRIN_API_KEY"])
res = drin.emails.send({
"from": {"email": "hello@acme.com", "name": "Acme"},
"to": [{"email": "maya@example.com"}],
"subject": "Your receipt",
"html": "<p>Thanks for your order.</p>",
}, idempotency_key="order-1042-receipt")npx -y @drin00/cli send \
--from "Acme <hello@acme.com>" \
--to maya@example.com \
--subject "Your receipt" \
--text "Thanks for your order." \
--idempotency-key order-1042-receiptimport nodemailer from "nodemailer";
const mail = nodemailer.createTransport({
host: "smtp.drin.run",
port: 587,
secure: false, // STARTTLS on 587; or port 465 with secure: true
auth: { user: "hello@acme.com", pass: process.env.DRIN_API_KEY },
});
await mail.sendMail({
from: "hello@acme.com",
to: "maya@example.com",
subject: "Your receipt",
html: "<p>Thanks for your order.</p>",
});The life of one email.
The request never waits on a mail server. You get a message id back at once, and the events follow.
Whichever way in
The REST API, the Node and Python SDKs, SMTP or the CLI all feed that one queue, with the same retries, block list and webhooks.Safe to retry
The same key replays the first result instead of sending twice, however long ago it was used. A different body with that key gets a 409.Your domain
Add it and get the records to publish. Where your DNS host supports it, approve them in one click.
Everything rides the same call.
Plain limits, and no surprises when something goes wrong.
Sending
Save one with merge fields and send it by name. Change the copy without a deploy.
Up to 100 emails a call. One bad address never fails the rest.
Up to 20 a message, 10 MB each, with inline images.
Set a time and it sends then. Up to 50 tags and extra headers on each message.
Events
The SDKs check the signature, and accept both while a secret rotates.
Five tries over 24 hours. Every attempt is in the delivery log.
Fixed your handler? Send the same payload again. A test ping is one call too.
The same events, kept 7 days, as a long poll or a live stream. No public URL needed.
Control
Every send path checks it first. Bounces and complaints can't be removed by mistake.
Every send reports what's left. A 429 says why and when to try again.
Bounces and complaints over 7 and 30 days, so a problem shows early.
Change the host, and your app sends through the same queue.
Your first send, in a minute.
Start free. Make a key, call the API and watch the events come back.