Set up Amazon SES

SES API v2 (SendEmail) through the AWS SDKs, signed with SigV4. Arqeno answers exactly as Amazon SES would, keeps every email in your Email inbox with its code, links, checks and simulated delivery events — and delivers nothing.

1. What to change

Endpoint for Amazon SES
https://api-arqeno.shriradhatechnologies.com/e/ses
Your key goes in
AWS-style credentials Arqeno issues for a key (SigV4)
Instead of
https://email.<region>.amazonaws.com
Works with
boto3 · AWS SDK v3
  1. Create SES credentials for an API key: API keys → the key's menu → SES credentials. The secret is shown once.
  2. Never use your real AWS keys here: these credentials are Arqeno's, made for staging only.
  3. Point the SES v2 client at the endpoint below (endpoint_url / endpoint, or AWS_ENDPOINT_URL_SESV2).

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

# staging only: the SDK reads these, your code doesn't change
AWS_ACCESS_KEY_ID=AKAR…            # from API keys → SES credentials
AWS_SECRET_ACCESS_KEY=…            # shown once when you create them
AWS_REGION=ap-south-1
AWS_ENDPOINT_URL_SESV2=https://api-arqeno.shriradhatechnologies.com/e/ses

Signed in, this guide has a Try it button that sends a sample email the Amazon SES way and reads its code back. Start free.

3. What Arqeno answers

The same status and body Amazon SES gives when it accepts an email (HTTP 200), so your code carries on as it would in production:

{"MessageId": "<email 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 Amazon SES 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 · MSG91 Email · Postmark · Mailgun · Brevo · ZeptoMail · SparkPost · Netcore Email · Mailjet · Mandrill