Skip to content
Live mail2x.com

Do not just send email. Know it was delivered.

Send DKIM-signed, SPF/DMARC-aligned transactional email from your own domain with one API call, and receive the recipient server’s acceptance as an event. Business mailboxes and webmail are in early access.

Live today: email sending API · business mail hosting and webmail in early access

POST /v1/emails
FromExample <[email protected]>
Toa***@example.org
SubjectYour monthly report is ready
SPF passDKIM passDMARC pass
  1. 09:30:00.084 Accepted202 · email.queued
  2. 09:30:00.311 Signed with DKIMd=example.com
  3. 09:30:00.402 Recipient server foundMX example.org
  4. 09:30:01.127 Delivered250 2.0.0 OK · email.delivered

Illustrative view · sample data

Capabilities

What is ready, what comes next

Every line states its status: use what is live today, help shape what is in early access.

Live

Sending API

Up to 50 recipients per call; text and/or HTML body, reply-to, tags.

Live

SPF · DKIM · DMARC

DKIM signature for your verified sending domain; direct delivery to the recipient server.

Live

Scheduling and validity

Schedule up to 30 days ahead with send_at; expired when validity ends.

Live

Delivery events

email.queued, delivered, failed, expired; signed webhooks and an event timeline.

Live

Encrypted content

Recipients and content are stored encrypted and never returned; OTP content is deleted on delivery.

Early access

Business mailboxes

Mailboxes, aliases, forwarding and webmail on your own domain.

Early access

Shared mailboxes

Team mailboxes with separate read, reply and send-as permissions.

Early access

Outbound policy

Domain allow lists, quotas and approval rules; sending stops on violation.

Use cases

Where it helps

01

Account and security mail

Password resets, sign-in alerts, verification links. With a short validity window.

02

Document and report notices

Invoice, payslip and monthly report notices; the delivery event links to your record.

03

Scheduled reminders

Queue appointment and renewal reminders in advance.

Developers

Start with a single request

Your first call once the sending domain is verified with a DNS record in the console. “delivered” means the recipient server accepted the message.

  • Base URL: https://api.reach2x.com
  • Bearer API key; permission per scope
  • Idempotency-Key required on sends
  • Errors as RFC 9457 problem+json with a stable code

Docs

curl Send an email
curl https://api.reach2x.com/v1/emails \
  -H "Authorization: Bearer $REACH2X_API_KEY" \
  -H "Idempotency-Key: rapor-2026-11-0001" \
  -H "Content-Type: application/json" \
  -d '{
    "from": { "email": "[email protected]", "name": "Example" },
    "to": "[email protected]",
    "subject": "Aylık raporunuz hazır",
    "text": "Raporunuz hazır: https://example.com/r/Ab12",
    "category": "informational"
  }'
Response202 Accepted
{
  "batch_id": "7d1c2e60-4a8b-4f0e-9b1a-2f6c1d9e3a10",
  "messages": [{
    "id": "c0a8f1e2-5b3d-4e7f-8a9b-1c2d3e4f5a6b",
    "object": "email",
    "status": "queued",
    "category": "informational",
    "from": "[email protected]",
    "to": "a***@example.org"
  }]
}
curl Register a webhook endpoint
curl https://api.reach2x.com/v1/webhooks \
  -H "Authorization: Bearer $REACH2X_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://example.com/hooks/2x",
    "events": ["sms.delivered", "sms.failed", "email.delivered", "email.failed"]
  }'
Response201 Created
{
  "webhook": {
    "id": "1b2c3d4e-5f60-4a7b-8c9d-0e1f2a3b4c5d",
    "url": "https://example.com/hooks/2x",
    "status": "active",
    "secret_prefix": "whsec_9fK2"
  },
  "secret": "whsec_… (shown only once)"
}
Security

Secure by default

The points below describe how the API behaves today, not future promises.

Scoped API keys

Each key belongs to one project and can only use the scopes it was given (e.g. sms.send, email.read). Only a hash is stored; the secret is shown once.

Tenant isolation

Asking for an id that belongs to another organization returns 404; nothing about its existence leaks.

Idempotency

Sending calls require an Idempotency-Key. A repeated request with the same key returns the original result instead of a second message.

Signed webhooks

Every event is signed with HMAC-SHA256 and carries a timestamp; failed deliveries are retried with growing intervals.

Masked recipients

Phone numbers and email addresses are masked in responses; message bodies can never be read back through the API.

Test keys

Keys starting with rx_test_ never deliver to a real recipient, so you can try your integration safely.

Pricing

Early access — pricing soon

The price list is not published yet. Open your account now, start on a trial entitlement and see the plans first when they are announced.

One product

Only the channel you need. No separate account, no separate portal.

Pricing soonEarly access

Several products

Add products to the same organization; keys, members and logs stay shared.

Pricing soonEarly access

The whole 2X family

Email, SMS, verification and the next channels under one organization.

Pricing soonEarly access

FAQ

Frequently asked questions

How do I verify my sending domain?

Add your domain in the console and publish the DNS TXT record plus the SPF/DKIM records shown. Sending from that domain opens once verification completes.

Does “delivered” mean the message was read?

No. It means the recipient mail server accepted the message (SMTP 250); it does not prove inbox placement or reading.

Can I send marketing email?

Not yet. Today the informational and otp categories are open; the commercial category will follow together with consent management.

Can I send attachments?

Attachments are not supported in this version. Share documents as links instead.

When will business mailboxes open?

Mail hosting and webmail are in early access; no date is fixed yet. Open an account to join the waiting list.

Open your account and send your first request today.

Sign-up is free. Try it with a test key without touching real recipients.