Move from Resend without rewriting your email code
Scribase Mail serves the Resend REST API shapes at mail-api.scribase.com. Seven steps, most of them configuration.
Scribase Mail is independent and not affiliated with Resend. Resend is a trademark of its owner.
Step 1
Create an account
Sign in at https://mail.scribase.com with a magic link; no password, no card. Create a team (we call it an account) and you are in the dashboard.
Step 2
Add and verify your sending domain
In the dashboard (Domains) or with POST /domains, add the domain you send from. Publish the DKIM, SPF and DMARC records it shows at your DNS provider, then press Verify or call POST /domains/:id/verify. The check reads live DNS.
Step 3
Create an API key
Create a key in the dashboard (API keys) and store it as a new secret, for example SCRIBASE_MAIL_KEY. Choose full_access, or sending_access optionally locked to one domain for app servers. Keys are sent the same way as before: Authorization: Bearer <key>.
Step 4
Point the SDK at the new base URL
The resend Node SDK takes a baseUrl option and also reads RESEND_BASE_URL. Either one works; nothing else in your sending code changes.
Node, resend SDK 6.xts import { Resend } from 'resend'; // Before: const resend = new Resend(process.env.RESEND_API_KEY); const resend = new Resend(process.env.SCRIBASE_MAIL_KEY, { baseUrl: 'https://mail-api.scribase.com', }); await resend.emails.send({ from: 'Acme <hello@acme.com>', to: ['you@example.com'], subject: 'It works', html: '<p>Sent through Scribase Mail.</p>', });Step 5
Send a test email first
Create an sk_test_ key: every send with it is simulated and never delivered, so you can run your whole flow without a verified domain. Recipients on test.scribase.dev script the outcome (delivered@test.scribase.dev, bounced@test.scribase.dev, complained@test.scribase.dev), so delivered, bounced and complained events each fire for real in your webhook handler.
Step 6
Move webhooks
Create the webhook endpoints again (dashboard or POST /webhooks) and store the new whsec_ signing secret. Payloads are signed in the Standard Webhooks format (webhook-id, webhook-timestamp, webhook-signature) and the same values are sent as svix-id, svix-timestamp and svix-signature, so resend.webhooks.verify() or the svix library keeps working.
Verifying a webhook in a Next.js route handlerts import { Resend } from 'resend'; const resend = new Resend(process.env.SCRIBASE_MAIL_KEY, { baseUrl: 'https://mail-api.scribase.com' }); export async function POST(req: Request) { const payload = await req.text(); // Scribase Mail signs in the Standard Webhooks format and also sends the // same values as svix-* headers, so the resend verifier works unchanged. const event = resend.webhooks.verify({ payload, headers: { id: req.headers.get('svix-id')!, timestamp: req.headers.get('svix-timestamp')!, signature: req.headers.get('svix-signature')!, }, webhookSecret: process.env.SCRIBASE_MAIL_WEBHOOK_SECRET!, // whsec_... }); // event.type: 'email.delivered', 'email.bounced', 'email.opened', ... return new Response('ok'); }Step 7
Switch traffic, then watch the first sends
Deploy with the new key and base URL. The dashboard shows each email with its events (GET /emails/:id/events) and every webhook delivery attempt. The Free plan caps at 100 emails a day; paid plans have no daily cap.
No SDK required
Any HTTP client works. These are the same request your code sends to Resend today, with a different host and key.
curl -X POST https://mail-api.scribase.com/emails \
-H "Authorization: Bearer $SCRIBASE_MAIL_KEY" \
-H "Content-Type: application/json" \
-d '{
"from": "Acme <hello@acme.com>",
"to": ["you@example.com"],
"subject": "It works",
"html": "<p>Sent through Scribase Mail.</p>"
}'import os
import requests
response = requests.post(
"https://mail-api.scribase.com/emails",
headers={"Authorization": f"Bearer {os.environ['SCRIBASE_MAIL_KEY']}"},
json={
"from": "Acme <hello@acme.com>",
"to": ["you@example.com"],
"subject": "It works",
"html": "<p>Sent through Scribase Mail.</p>",
},
timeout=30,
)
response.raise_for_status()
print(response.json()["id"])# No code change: the resend SDK reads this variable
RESEND_BASE_URL=https://mail-api.scribase.comWhat is supported
Every route below is served at mail-api.scribase.com in the Resend request and response shape, with Resend-style error bodies.
| Emails | POST /emails · POST /emails/batch · GET /emails · GET /emails/:id · PATCH /emails/:id (reschedule) · POST /emails/:id/cancel · GET /emails/:id/events · GET /emails/:id/webhook-deliveries |
| Domains | POST /domains · GET /domains · GET /domains/:id · PATCH /domains/:id · DELETE /domains/:id · POST /domains/:id/verify |
| API keys | POST /api-keys · GET /api-keys · DELETE /api-keys/:id |
| Webhooks | POST /webhooks · GET /webhooks · GET /webhooks/:id · PATCH /webhooks/:id · DELETE /webhooks/:id · GET /webhooks/:id/deliveries |
| Suppressions | GET /suppressions · POST /suppressions · DELETE /suppressions/:address |
| Usage and billing | GET /usage · GET /audit-log · GET /billing · GET /billing/plans |
| Teams | GET, POST /accounts · GET, PATCH /accounts/:id · GET, POST /accounts/:id/members · PATCH, DELETE /accounts/:id/members/:userId |
| Sign-in emails for your app | POST /auth/magic-link · POST /auth/otp · POST /auth/otp/verify · GET /auth/verify · GET /.well-known/jwks.json |
Sends accept from, to (up to 50), cc, bcc, reply_to, subject, html, text, custom headers, attachments (content or path, inline by content id), tags, scheduled_at (up to 30 days ahead) and the Idempotency-Key header. Batches take up to 100 emails.
Not supported yet
- Contacts, audiences, segments and topics (/contacts, /audiences, /segments)
- Broadcasts and templates (/broadcasts, /templates)
- Inbound email (/emails/received) and attachment download
- Automations, the Inboxes API and OAuth apps
Missing something you rely on? Email support@scribase.com.