Set up Netcore Email

Netcore Cloud (Pepipost) email API, v5 and v6. Arqeno answers exactly as Netcore 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

Base URI for Netcore Email
https://api-arqeno.shriradhatechnologies.com/e/netcore/v5
Your key goes in
the api_key header (v5) or Authorization: Bearer (v6)
Instead of
https://emailapi.netcorecloud.net/v6 (v5: https://api.pepipost.com/v5)
Works with
pepipost SDKs · HTTP
  1. v5 (the pepipost SDKs): set Configuration.BASEURI / base_uri to the URI below. v6: use …/e/netcore/v6.
  2. Send an Arqeno key as api_key (v5) or as a Bearer token (v6).
  3. Each personalization is captured as its own email, its [%ATTRIBUTES%] 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

curl -X POST "https://api-arqeno.shriradhatechnologies.com/e/netcore/v5/mail/send" -H "api_key: arq_YOUR_KEY" -H "content-type: application/json" \
  -d '{"from": {"email": "noreply@acme.com"}, "subject": "Your code is [%CODE%]", "content": [{"type": "html", "value": "<p>Your code is [%CODE%]</p>"}], "personalizations": [{"to": [{"email": "someone@example.com"}], "attributes": {"CODE": "482913"}}]}'

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

3. What Arqeno answers

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

{"data": {"message_id": "<request id>"}, "message": "OK", "status": "success"}

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 Netcore 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 · MSG91 Email · Postmark · Mailgun · Brevo · ZeptoMail · SparkPost · Mailjet · Mandrill