Live reach2x.com

Every relationship. One workspace.

Name: Reach2X
Brand: 2X

2X brings email, SMS, verification codes and the next channels under one organization account, one API key and one event log. Start with the sending API today and help shape the unified inbox in early access.

Start free Documentation

Live today: email sending API and signed webhooks · SMS and OTP launching · unified inbox in early access

api.reach2x.com/v1

Mail2X Live

Relay2X Live

TXT2X Launching

OTP2X Launching

WA2X Early access

NOTI2X Early access

PUSH2X Early access

Your app REST · webhook

Reach2X API /v1

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

Email sending API

From your verified domain, SPF, DKIM and DMARC aligned, delivered straight to the recipient’s server.

Live

Signed webhook events

queued, delivered, failed and expired events, HMAC-signed with retries.

Live

Projects and scoped keys

Live and test projects; every key uses only its own scopes.

Launching

SMS sending API

İYS category, approved sender names and scheduling. Operator connection is launching.

Launching

Verification codes (OTP)

Time-limited one-time codes over SMS or email; the body is never stored.

Early access

Unified inbox

A workspace that gathers email, SMS and chat conversations for one team.

Early access

Customer profile

Permitted interactions from every channel on a single contact card.

Early access

Campaigns and segments

Email and SMS campaigns tied to consent and opt-out records.

Use cases

Where it helps

Product notifications

Order, invoice and report notices to email today, to phones with the same call shape when SMS opens.

One event log

Collect delivery events of every channel at one webhook endpoint; support looks in one place.

Multi-product organization

Shared members, roles and audit log; each team sees only the products it is entitled to.

Developers

Start with a single request

Same key, same Idempotency-Key rule, same response shape. The channel changes, your integration does not.

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 Send an SMS

curl https://api.reach2x.com/v1/sms \
  -H "Authorization: Bearer $REACH2X_API_KEY" \
  -H "Idempotency-Key: randevu-48213" \
  -H "Content-Type: application/json" \
  -d '{
    "to": "+905321234567",
    "body": "Randevunuz 18 Kasım 14:30. Değişiklik: https://example.com/r/Ab12",
    "category": "informational",
    "sender": "EXAMPLE"
  }'

Response202 Accepted

{
  "batch_id": "3f9a2b7c-1d4e-4a5b-8c6d-7e8f9a0b1c2d",
  "messages": [{
    "id": "8b7a6c5d-4e3f-4a2b-9c1d-0e9f8a7b6c5d",
    "object": "sms",
    "status": "queued",
    "to": "+90 5** *** ** 67",
    "sender": "EXAMPLE",
    "segments": 1,
    "encoding": "gsm7_tr"
  }]
}

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

What is the difference between 2X and Reach2X?

2X is the product family. Reach2X is both the shared sending API and the unified communication workspace in development. The other 2X products build on the same account and API.

What can I really use today?

The email sending API, webhook events, projects and scoped API keys are live. SMS and OTP are launching; unified inbox, WhatsApp, notification orchestration and push are in early access.

When will pricing be announced?

The price list is not published yet. If you open an account you will see the plans in the console when they are announced.

Do I need a separate account per product?

No. You open one organization account and add products to it. Members, keys and the audit log are shared.

Can I test without touching real recipients?

Yes. A test project key (rx_test_) never delivers to a real recipient; statuses and webhooks still flow.

2X family