Now liveConnect any mailbox in one call

Communication APIs for Modern SaaS, built to scale

Skip the OAuth dance, the DNS records, and the provider quirks. One API handles it all.

  • 99.99% Uptime SLA
  • p95 84ms Response time
  • SOC 2 Type II

Every connector. One dashboard. Zero context-switching.

Product dashboard

Everything you need to connect, schedule & send

A composable set of infrastructure APIs — each with predictable REST endpoints and consistent JSON responses.

Google OAuth

Hosted auth. Encrypted tokens. Zero boilerplate.

  • Encrypted token storage
  • Automatic refresh handling
  • Per-tenant isolation
POST/v1/google/connect

Returns a Google consent URL. Redirect your user there to link their mailbox — you never handle their password.

Request
{
  "application_id": "app_7f2c91",
  "email": "founder@company.com"
}
Response200 OK
{
  "authUrl": "https://accounts.google.com/o/oauth2/v2/auth?…",
  "email": "founder@company.com"
}

Google Calendar

Read and write calendar events like they're your own database.

  • Read, create, and manage events
  • Uses connected account tokens
  • calendar.event.* webhooks
POST/v1/calendar/events

Creates the event on the connected Google Calendar and returns it, link included.

Request
{
  "connection_id": "conn_4f10",
  "summary": "Quarterly sync",
  "start": { "date_time": "2026-07-08T10:00:00Z", "time_zone": "UTC" },
  "end":   { "date_time": "2026-07-08T10:30:00Z", "time_zone": "UTC" }
}
Response200 OK
{
  "id": "evt_92aa",
  "summary": "Quarterly sync",
  "status": "confirmed",
  "html_link": "https://calendar.google.com/event?eid=…"
}

Email Sending

SES-backed delivery without touching AWS.

  • Delivered through AWS SES
  • Delivery & bounce webhooks
  • Verified sending domains
POST/v1/emails/send

Hands the message to AWS SES and tells you exactly which recipients were accepted and which bounced.

Request
{
  "application_id": "app_7f2c91",
  "from": "founder@company.com",
  "to": "customer@example.com",
  "subject": "Welcome",
  "html": "<p>Your account is ready.</p>"
}
Response200 OK
{
  "messageId": "<a1b2c3@mail.company.com>",
  "accepted": ["customer@example.com"],
  "rejected": null
}

DNS Management

SPF, DKIM, DMARC — verified automatically, not manually.

  • SPF, DKIM & DMARC managed
  • Automatic record verification
  • Tracking records included
POST/v1/dns/domains

Registers a sending domain and hands back the exact SPF, DKIM, and DMARC records to publish.

Request
{
  "domain": "mail.company.com"
}
Response200 OK
{
  "id": "dom_abc123",
  "domain": "mail.company.com",
  "status": "pending",
  "records": [
    { "type": "TXT",   "name": "@",             "purpose": "spf" },
    { "type": "CNAME", "name": "s1._domainkey", "purpose": "dkim" },
    { "type": "TXT",   "name": "_dmarc",        "purpose": "dmarc" }
  ]
}

SMTP API

REST in, email out. No credentials to leak.

  • No SMTP credentials to store
  • Same pipeline as /v1/emails/send
  • Signed webhook receipts
POST/v1/smtp/send

Sends through a mailbox you connected by IMAP/SMTP — same delivery pipeline, no credentials in your app.

Request
{
  "application_id": "app_7f2c91",
  "from": "alerts@company.com",
  "to": "ops@example.com",
  "subject": "Deploy finished",
  "text": "Build 412 is live."
}
Response200 OK
{
  "messageId": "<d4e5f6@mail.company.com>",
  "accepted": ["ops@example.com"],
  "rejected": null
}

Designed for developers

The API you wish every provider shipped with. No SDK sprawl, no provider-specific quirks.

api.reinterface.com
// Request
POST /v1/emails/send

{
  "application_id": "app_7f2c91",
  "from": "founder@company.com",
  "to": "customer@example.com",
  "subject": "Welcome",
  "html": "<p>Your account is ready.</p>"
}

// Response
{
  "messageId": "<a1b2c3@mail.company.com>",
  "accepted": ["customer@example.com"],
  "rejected": null
}

Simple REST API

Predictable endpoints with consistent JSON responses.

Secure API keys

Scoped keys with environment separation built in.

Real-time webhooks

Delivery, bounce, and OAuth events pushed to your app.

SDKs: TypeScript · Python · Go · OpenAPI 3.1

API reference

Security isn’t a feature. It’s the foundation.

Your keys never touch a browser — every credential and payload is protected end to end.

Encrypted token storage
OAuth tokens encrypted at rest with per-tenant isolation.
API key rotation
Rotate keys without downtime using overlapping validity windows.
Least-privilege OAuth scopes
Request only the Google scopes your product actually needs.
Signed webhooks
Verify every webhook payload with HMAC signatures.

Questions, answered straight.

What the API does, which mailboxes it reaches, and what’s honestly still ahead — no hedging.

One REST API. Connect a mailbox by OAuth or by credentials, then move mail — POST /send to send, POST /fetch to pull. No SDK; the same request shape works from any language that can make an HTTP call.