Set up ZeptoMail
Zoho ZeptoMail: single, batch and template sends. Arqeno answers exactly as ZeptoMail would, keeps every email in your Email inbox with its code, links, checks and simulated delivery events — and delivers nothing.
1. What to change
https://api-arqeno.shriradhatechnologies.com/e/zeptomail/- Your key goes in
- the Authorization header: Zoho-enczapikey <key>
- Instead of
https://api.zeptomail.com/- Works with
- Node SDK · HTTP
- Point the SendMailClient's url at the one below (it keeps the path).
- Send an Arqeno key as the token: Zoho-enczapikey followed by the key.
- Batch sends capture one email per recipient with its merge_info; templates are recorded, not rendered.
Need a key? Create a free workspace and make one on its API keys page — it starts with arq_. The same key works for SMS and every email provider.
Good to know
Over plain http (local dev only) the Node SDK also needs { useHttps: false } as its second argument.
2. Send a test email
import { SendMailClient } from "zeptomail";
// staging only: url points the client at Arqeno, the token carries an Arqeno key
const client = new SendMailClient({ url: process.env.ZEPTOMAIL_URL ?? "https://api-arqeno.shriradhatechnologies.com/e/zeptomail/",
token: `Zoho-enczapikey ${process.env.ZEPTOMAIL_KEY}` });
await client.sendMail({ from: { address: "noreply@acme.com", name: "Acme" },
to: [{ email_address: { address: "someone@example.com" } }],
subject: "Your code is 482913", textbody: "Your code is 482913" });Signed in, this guide has a Try it button that sends a sample email the ZeptoMail way and reads its code back. Start free.
3. What Arqeno answers
The same status and body ZeptoMail gives when it accepts an email (HTTP 200), so your code carries on as it would in production:
{"data": [{"code": "EM_104", "additional_info": [], "message": "OK"}], "message": "OK", "request_id": "<request id>"}The email shows up in the Email inbox at once: its code and magic link to copy, a safe preview, attachments, and Checks — links to staging hosts, unfilled placeholders, a spam score and email-client support.
4. Read the code in your tests
One call waits up to 30 seconds for the newest email to an address and hands back its code and magic link — whichever provider sent it. The address goes in the body, never in a URL.
curl -X POST "https://api-arqeno.shriradhatechnologies.com/v1/otp/wait" \
-H "Authorization: Bearer arq_YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{"to": "someone@example.com", "wait": 25}'
# → {"channel": "email", "code": "482913", "magicLink": "https://…", "subject": "…", …}5. Test bounces and complaints
Nothing is delivered, but every email gets the events ZeptoMail would report. Send to an address with a tag — asha+bounced@acme.test, +complained, +delayed, +suppressed — and read the events back.
# send to asha+bounced@acme.test (or bounced@resend.dev), then:
curl "https://api-arqeno.shriradhatechnologies.com/v1/events?type=email.bounced" -H "Authorization: Bearer arq_YOUR_KEY"
# → {"items": [{"type": "email.bounced", "recipient": "asha+bounced@acme.test",
# "detail": {"smtpCode": "550", "enhancedCode": "5.1.1", …}, …}], "nextAfter": "…"}Other email providers
SMTP · Resend · SendGrid · Amazon SES · MSG91 Email · Postmark · Mailgun · Brevo · SparkPost · Netcore Email · Mailjet · Mandrill