Set up MSG91 Email
MSG91's Email API v5, template sends with variables. Arqeno answers exactly as MSG91 Email 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/msg91/api/v5/email/send- Your key goes in
- the authkey header
- Instead of
https://control.msg91.com/api/v5/email/send- Works with
- HTTP API
- Replace MSG91's email URL with the one below.
- Send an Arqeno key as authkey.
- Each entry in recipients is its own email. MSG91 renders its own template, so Arqeno keeps the template id and the variables: an OTP passed as a variable (otp, code) is what the OTP wait returns.
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
curl -X POST "https://api-arqeno.shriradhatechnologies.com/e/msg91/api/v5/email/send" \
-H "authkey: arq_YOUR_KEY" -H "accept: application/json" -H "content-type: application/json" \
-d '{"recipients": [{"to": [{"name": "Asha", "email": "someone@example.com"}], "variables": {"otp": "482913"}}],
"from": {"name": "Acme", "email": "noreply@acme.mailer91.com"}, "domain": "acme.mailer91.com",
"template_id": "global_otp"}'Signed in, this guide has a Try it button that sends a sample email the MSG91 Email way and reads its code back. Start free.
3. What Arqeno answers
The same status and body MSG91 Email gives when it accepts an email (HTTP 200), so your code carries on as it would in production:
{"data": {"unique_id": "<request id>"}, "errors": {}, "status": "success", "message": "Thank you. Your request has been queued.", "hasError": false}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 MSG91 Email 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 · Postmark · Mailgun · Brevo · ZeptoMail · SparkPost · Netcore Email · Mailjet · Mandrill