Set up Mandrill
Mailchimp Transactional (Mandrill): send and send-template. Arqeno answers exactly as Mandrill 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/mandrill/api/1.3- Your key goes in
- key in the JSON body, where your Mandrill key goes
- Instead of
https://mandrillapp.com/api/1.3- Works with
- Node · Python SDKs
- The SDKs have no base-URL option: set the client's basePath (Node) or api_client.host (Python) to the one below.
- Use an Arqeno key as the Mandrill key.
- Recipients share one email unless merge_vars personalise them; *|MERGE|* tags are filled in.
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.
2. Send a test email
const mailchimp = require("@mailchimp/mailchimp_transactional")(process.env.MANDRILL_API_KEY);
// staging only: basePath points the client at Arqeno, the key is an Arqeno key
mailchimp.basePath = process.env.MANDRILL_BASE_PATH ?? "https://api-arqeno.shriradhatechnologies.com/e/mandrill/api/1.3";
await mailchimp.messages.send({ message: { from_email: "noreply@acme.com", to: [{ email: "someone@example.com" }],
subject: "Your code is 482913", text: "Your code is 482913" } });Signed in, this guide has a Try it button that sends a sample email the Mandrill way and reads its code back. Start free.
3. What Arqeno answers
The same status and body Mandrill gives when it accepts an email (HTTP 200), so your code carries on as it would in production:
[{"email": "…", "status": "sent", "_id": "<email id>", "reject_reason": null, "queued_reason": null}]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 Mandrill 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 · ZeptoMail · SparkPost · Netcore Email · Mailjet