Skip to content

REST API Reference & Endpoints

Last updated 28 October 2026

A small surface, deliberately. Every endpoint here earns its place. Download the official Postman Collection (/sadasend.postman_collection.json) for 1-click endpoint testing and sandbox debugging.

SadaSend REST APIs, Port 587 ESMTP submission relay, hosted MCP tools for AI agents, and official zero-dependency TypeScript and Python SDKs are live in production. Every account receives 6,000 monthly transactional emails with strict server-enforced guardrails.

Architecture, Base URL & Request Protocol

• Production Base URL: https://api.sadasend.com (canonical root-mounted endpoints, e.g. POST /emails, POST /keys).

• Authentication: Bearer token via HTTP header: Authorization: Bearer sada_live_sk_....

• Standard Headers: Content-Type: application/json, and optional Idempotency-Key: <uuid-v4> for transactional deduplication.

• Rate Limit Headers: X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset returned on every response.

• Standard Error Envelope: RFC 7807 JSON error responses with error.code, error.message, and HTTP status code.

Emails

EndpointDoes
POST /emailsSend one. html, text, template + variables, or raw MIME stream (message/rfc822). Supports stream (transactional, notification, broadcast), verifyBeforeSend, cc, bcc, reply_to, tags, utm tracking, attachments, scheduled_at, dry_run, mode ("approval"), hold_reason, channel, source, and agent_name
POST /emails/batchUp to 100 per call, each independently accepted or rejected, preserving per-email provenance and utm parameters
GET /emails/:idStatus, full event trail, rendered body, and origin provenance (channel, source, agentName)
GET /emailsFilter by status, recipient, domain, date, tag, channel (mcp, sdk, api, smtp), stream (transactional, notification, broadcast), source, and agent_name
DELETE /emails/:idCancel a scheduled send before it leaves the queue
POST /emails/:id/resendSend it again with the key that sent it. Refused if that key was revoked or the body has aged out
GET /emails/exportThe log as CSV or JSON, streamed. Same filters as GET /emails, plus from and to dates
POST /tools/verifySynchronous pre-send deliverability check (syntax, MX lookups, disposable burner detection, domain typo autocorrect)
GET /inbound/routesList active inbound MX routing rules, priority orders, and destination webhook endpoints
POST /inbound/routesCreate pattern-matched inbound route (support@*, *@inbound.domain.com) with signature stripping and clean markdown extraction
POST /inbound/simulateSimulate inbound message parsing and routing without sending live network emails
POST /dmarc/reportsUpload RFC 7489 aggregate DMARC feedback XML (.xml, .gz, .zip) for automated SPF/DKIM alignment scoring
GET /dmarc/domains/:domain/summaryAggregate DMARC deliverability scorecard for one domain, with spoofing threats and a policy upgrade path (GET /dmarc/threats lists threats across domains)
POST /inboxes/ephemeralAllocate a short-lived agent inbox (default domain auth.sadasend.com) that receives real mail and extracts one-time codes (Pro and Scale)
POST /testing/wait-for-codeWait for and extract 6-digit OTP verification codes or magic links in sub-150ms for automated test suites
POST /inbound/parseContext-safe inbound email parser with clean markdown conversion, signature stripping, and prompt injection threat scoring

Sending an email

The API never calls the sending provider synchronously. You get an id in milliseconds; delivery happens on a worker and is reported through webhooks or by polling the message.

JSON
POST /emails
{
  "from": "you@yourdomain.com",
  "to": "user@example.com",
  "cc": ["team@example.com"],
  "bcc": ["compliance@yourdomain.com"],
  "reply_to": "support@yourdomain.com",
  "subject": "Welcome aboard",
  "html": "<p>Get started with our <a href="https://yourdomain.com/dashboard">Dashboard</a>.</p>",
  "utm": {
    "source": "newsletter",
    "medium": "email",
    "campaign": "onboarding_flow",
    "content": "dashboard_link"
  },
  "agent_name": "Claude Support Agent",
  "source": "agent"
}

202 Accepted
{ "id": "26abdd24-36a9-475d-83bf-4d27a31c7def", "status": "queued" }

Agent and Channel Provenance

Every email carries origin provenance tracking who and what sent it:

• channel: Ingress protocol — api (standard REST), sdk (Node/Python clients), mcp (Model Context Protocol), or smtp (MTA relay).

• source: Sending persona — agent (autonomous AI bots), backend (application services), automation (scheduled cron jobs), or system (platform transactional alerts).

• agent_name: An optional identifier (up to 128 chars) attributing the email to a specific bot, e.g. "LeadGen AutoGPT" or "Claude 3.7 Assistant".

You can set provenance explicitly in the JSON body (agent_name, source), pass zero-code headers (X-SadaSend-Agent, X-SadaSend-Source), or configure default personas directly on your API keys.

HTTP
POST /emails
Authorization: Bearer sada_live_sk_…
X-SadaSend-Agent: LeadGen AutoGPT
X-SadaSend-Source: agent
Content-Type: application/json

{
  "from": "sales@yourdomain.com",
  "to": "prospect@target.com",
  "subject": "Partnership inquiry",
  "text": "Hello, reaching out regarding your API needs."
}

Transactional stream priority & IP pool isolation

Prevent critical authentication emails (OTP codes, password resets, magic links, receipts) from getting delayed behind marketing campaigns or bulk notifications.

SadaSend isolates outbound dispatch across distinct IP pools based on message stream. By default, commercial emails route over standard broadcast pools. To guarantee high-reputation transactional delivery, pass X-SadaSend-Stream: transactional or include "transactional", "auth", or "otp" in your tags array:

HTTP
POST /emails
Authorization: Bearer sada_live_sk_…
X-SadaSend-Stream: transactional
Content-Type: application/json

{
  "from": "auth@yourdomain.com",
  "to": "user@example.com",
  "subject": "Your 6-digit verification code: 849201",
  "text": "Your login code is 849201. It expires in 10 minutes.",
  "tags": ["auth", "otp"]
}

Batch sending

Send up to 100 emails in a single atomic HTTP request with POST /emails/batch.

Every message is evaluated independently through acceptMessage. A suppressed recipient or allowlist block on message #42 never fails the rest of the batch — each message gets its own outcome in the results array.

The call always returns 207 Multi-Status inside the 2xx range. Each item derives its own idempotency key (${Idempotency-Key}:${index}), so retrying the whole batch safely replays accepted messages while retrying failed ones.

JSON
POST /emails/batch
Authorization: Bearer sada_live_sk_…
Idempotency-Key: batch-2026-09-07-001
Content-Type: application/json

{
  "emails": [
    {
      "from": "notifications@yourdomain.com",
      "to": "alice@example.com",
      "subject": "Order #1201 Confirmed",
      "html": "<p>Hi Alice, your order is confirmed.</p>",
      "tags": ["orders"]
    },
    {
      "from": "notifications@yourdomain.com",
      "to": "bob@example.com",
      "subject": "Order #1202 Confirmed",
      "html": "<p>Hi Bob, your order is confirmed.</p>",
      "tags": ["orders"]
    }
  ]
}

207 Multi-Status
{
  "accepted": 2,
  "refused": 0,
  "total": 2,
  "results": [
    { "index": 0, "ok": true, "id": "4092b1a8-36a9-475d-83bf-4d27a31c7def", "status": "queued" },
    { "index": 1, "ok": true, "id": "91a4f8c2-12e4-49fb-9ac7-1b32d849fae0", "status": "queued" }
  ]
}

Listing and searching messages

GET /emails queries message activity with keyset-based cursor pagination. Unlike offset pagination, keyset cursors stay stable and performant as new emails are continuously ingested.

Filter by status (e.g. queued, delivered, bounced), recipient or subject search (q), labels (tag), and provenance dimensions (channel, source, agent_name).

JSON
GET /emails?channel=mcp&source=agent&status=delivered&limit=25
Authorization: Bearer sada_live_sk_…

200 OK
{
  "messages": [
    {
      "id": "26abdd24-36a9-475d-83bf-4d27a31c7def",
      "from": "support@yourdomain.com",
      "to": "customer@example.com",
      "subject": "Ticket resolved",
      "status": "delivered",
      "channel": "mcp",
      "source": "agent",
      "agentName": "Billing Resolver",
      "tags": ["support"],
      "createdAt": "2026-09-07T12:00:00.000Z"
    }
  ],
  "total": 1,
  "nextCursor": null
}

Streaming message export

GET /emails/export streams your message history up to 100,000 rows as csv, json, or jsonl (NDJSON). Rows are fetched in keyset batches and streamed immediately rather than buffered in server memory.

Supports all filters from GET /emails, plus from and to ISO timestamps to bound the export window.

HTTP
GET /emails/export?format=csv&channel=mcp&from=2026-09-01T00:00:00Z&to=2026-09-07T23:59:59Z
Authorization: Bearer sada_live_sk_…

200 OK
Content-Type: text/csv; charset=utf-8
Content-Disposition: attachment; filename="sadasend-messages-2026-09-07.csv"

id,created_at,from,to,subject,status,channel,source,agent_name,tags
26abdd24-…,2026-09-07T12:00:00.000Z,support@yourdomain.com,customer@example.com,"Ticket resolved",delivered,mcp,agent,"Billing Resolver","support"

Resending and cancelling

POST /emails/:id/resend re-dispatches a message under its original issuing key. Because this creates a new send with its own event trail, it runs through acceptMessage to verify recipient suppressions and current quota.

DELETE /emails/:id (or POST /emails/:id/cancel) removes a message while it is still in queued status, deleting it from the internal outbox worker before it leaves for the mail provider.

Copies and replies

cc and bcc take one address or several, exactly as to does. Both are recipients in every sense that matters: they count against your quota, and they are checked against the key’s recipient allowlist and your suppression list. Putting an address in bcc is not a way around a guardrail.

bcc is stored on the message so the log can answer who received it, and is never written into the message itself. reply_to is not a recipient — it costs no quota and is checked against neither the allowlist nor suppression.

JSON
{
  "from": "you@yourdomain.com",
  "to": "user@example.com",
  "cc": ["colleague@example.com"],
  "bcc": ["archive@yourdomain.com"],
  "reply_to": "support@yourdomain.com",
  "subject": "Welcome aboard",
  "html": "<strong>It works.</strong>"
}

Tags

Up to ten labels on a message, lowercased and de-duplicated so Welcome and welcome are one tag rather than two rows in a breakdown nobody can read.

They earn their place on the stats: GET /account/stats?by_tag=true gives each tag its own bounce and complaint rate, against its own send count. "Your bounce rate is 2%" is a number nobody can act on; "your bounce rate is 2% and all of it is the invite email" is a fix.

On the log, repeat ?tag= to narrow — ?tag=billing&tag=retry is the billing retries, not billing plus retries.

JSON
{ "from": "…", "to": "…", "subject": "…", "html": "…", "tags": ["welcome", "onboarding"] }

Open and click tracking

Both are off on every account. Turn them on with PATCH /account — { "trackOpens": true }, { "trackClicks": true } — and GET /account reports the current state.

With opens on, a 1×1 image is appended to your HTML and a fetch records an opened event. With clicks on, links are rewritten to pass through a redirect that records a clicked event and then sends the recipient to your original URL. Neither records the recipient’s IP address or user agent.

Two things are deliberately never rewritten: the one-click unsubscribe link, which must not gain a hop, and any URL containing template variables, because it is not known until the message renders.

GET /account/stats?engagement=true adds opens and clicks. Each counts messages opened or clicked at least once, not events — four views of one email is not a 400% open rate. Each block is absent unless that tracking is on, because "not measured" is a different statement from zero.

tracked is the denominator, and it is not sent. It counts only the messages that actually carried a pixel or a rewritten link: mail sent before you turned tracking on has neither and can never report an open, and neither can a text-only message or HTML with nothing clickable in it. Dividing by sent would report those as unopened and quietly deflate your rate — so the rate is against what was measurable, not against everything you sent.

JSON
PATCH /account
{ "trackOpens": true, "trackClicks": true }

GET /account/stats?window=14d&engagement=true
{
  "window": "14d",
  "sent": 1200,
  "opens":  { "tracked": 800, "opened": 486, "openRate": 60.75 },
  "clicks": { "tracked": 640, "clicked": 91, "clickRate": 14.22 }
}

Why a message bounced

Bounce and complaint events carry a classification: hard the address does not exist, soft temporarily undeliverable, block the receiver refused the mail on policy or content, spam the recipient pressed the button. Every other event type carries null.

The distinction is the whole point. A bounce rate made of soft bounces is a retry problem; the same rate made of blocks is a reputation problem, and the thing to change is on your side. unknown means the provider could not say — not that it was minor.

Deterministic dry-run status return

Pass dry_run: true on POST /emails to execute end-to-end payload validation, template rendering, and suppression checking without touching mailbox providers or burning credit quota.

Instead of ambiguous queued states, SadaSend returns a deterministic contract with status: "simulated" and an ID prefixed with sim_ (e.g., sim_018f92ab3c4d5e6f7a8b9c0d), accompanied by simulated: true and the pre-rendered email payload (rendered). This enables client SDKs, autonomous coding agents, and CI pipelines to branch strictly on simulation vs real delivery without ambiguous side-effects.

JSON
{
  "id": "sim_018f92ab3c4d5e6f7a8b9c0d",
  "status": "simulated",
  "simulated": true,
  "dryRun": true,
  "rendered": {
    "from": "notifications@yourdomain.com",
    "to": ["client@example.com"],
    "subject": "Preflight Validation",
    "html": "<p>Testing simulation pipeline.</p>"
  }
}

Message stream isolation & RFC 8058 unsubscribe guardrails

SadaSend enforces strict message stream separation across three delivery tiers to protect sender reputation while preventing accidental unsubscription from critical account messages:

• Transactional Stream (`stream: "transactional"`, Default): Reserved exclusively for password resets, 2FA/OTP login codes, billing receipts, and legal notifications. RFC 8058 1-click unsubscribe headers are strictly omitted from this stream, guaranteeing that a recipient clicking an email unsubscribe link in a newsletter cannot accidentally silence security-critical verification messages.

• Notification Stream (`stream: "notification"`): For account activity digests, team invitations, and product notifications. SadaSend automatically injects RFC 8058 1-click unsubscribe headers (List-Unsubscribe-Post: List-Unsubscribe=One-Click and List-Unsubscribe: <https://api.sadasend.com/unsubscribe/...>), maintaining mailbox provider compliance (Gmail, Yahoo, Outlook) while isolating notification reputation from your core authentication stream.

• Broadcast Stream (`stream: "broadcast"`): For marketing updates and newsletters. Dispatches are strictly filtered against your account suppression list and mandate RFC 8058 1-click unsubscribe headers.

Pass the stream in the JSON payload ("stream": "transactional" | "notification" | "broadcast") or via the X-SadaSend-Stream HTTP header.

HTTP
POST /emails
Authorization: Bearer sada_live_sk_…
Content-Type: application/json
X-SadaSend-Stream: transactional

{
  "from": "auth@yourdomain.com",
  "to": "user@example.com",
  "subject": "Your verification code: 829104",
  "html": "<p>Your login code is <strong>829104</strong>. Valid for 15 minutes.</p>",
  "stream": "transactional"
}

High-throughput streaming MIME ingestion (message/rfc822)

For high-frequency mail services, SMTP forwarders, and streaming microservices, SadaSend supports direct raw MIME ingestion via POST /emails with Content-Type: message/rfc822.

Instead of buffering multi-megabyte multipart MIME strings in RAM or converting attachments into Base64 JSON strings, pass a raw RFC 5322 MIME stream directly in the request body. SadaSend streams the payload straight to the outbox queue with zero memory buffering.

HTTP
POST /emails
Authorization: Bearer sada_live_sk_…
Content-Type: message/rfc822
X-SadaSend-Stream: notification

From: alerts@yourdomain.com
To: devops@example.com
Subject: Production Deployment Complete
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8

Deployment v0.2.23 was successfully deployed to production.

Outbound DLP & Loop Breakers

Autonomous agents running in automated loops can accidentally enter infinite retry cycles or hallucinate sensitive internal credentials into message bodies. SadaSend provides two built-in safety controls at dispatch:

• 5-Minute Content-Hash Loop Circuit Breaker: Calculates a rolling SHA-256 fingerprint over recipient sets, subject lines, and normalized body text. If an identical email is re-sent to the same recipient within 5 minutes (300 seconds), SadaSend transparently deduplicates the send ({ ok: true, deduplicated: true }). The original message ID is echoed without burning extra monthly quota or spamming the recipient’s inbox. Broadcast newsletters to different recipients are never deduplicated.

• Outbound Secret & PII Scanner (DLP): Inspects subject, text, and HTML for leaked API tokens (Anthropic, OpenAI, AWS, GitHub, Stripe, Slack, etc.), cryptographic private keys (RSA, OpenSSH, EC), payment card numbers (Luhn validated), and SSNs. Refuses with HTTP 422 dlp_secret_detected and provides a safe redacted preview (sk-ant***abc).

• Diagnostic Opt-Out: Trusted internal diagnostic tools or debug scripts can pass "dlp": false in the request body to bypass DLP pattern evaluation.

HTTP
POST /emails
Authorization: Bearer sada_live_sk_…
Content-Type: application/json

{
  "from": "agent@yourdomain.com",
  "to": "client@example.com",
  "subject": "System status update",
  "html": "<p>Server logs: token=sk-ant-api03-abcdef1234567890...</p>"
}

422 Unprocessable Entity
{
  "error": "dlp_secret_detected",
  "message": "Outbound DLP scanner blocked email containing exposed Anthropic API token",
  "preview": "sk-ant***890",
  "location": "html",
  "docs": "https://www.sadasend.com/docs/errors#dlp_secret_detected"
}

Context-Safe Inbound Email Parsing

Designed specifically for autonomous AI agents and customer support bots ingesting incoming replies via POST /inbound/parse:

• RFC 5322 Thread Stitching: Stitches In-Reply-To and References headers into a consistent conversation threadId and calculates hierarchy depth.

• Token-Efficient Clean Markdown: Strips noisy quoted history chains (> ..., On ... wrote:), legal disclaimers, and mobile signatures, compressing message volume by ~85% to preserve LLM context windows.

• Prompt Injection Risk Classification: Runs fast edge heuristics against inbound text and HTML, assigning an injection risk score (0.0 to 1.0) and tagging quarantineRecommended: true if jailbreaks, system prompt overrides, or delimiter tricks are detected.

Accepts either raw RFC 822 MIME (Content-Type: message/rfc822) or structured JSON payloads (Content-Type: application/json).

HTTP
POST /inbound/parse
Authorization: Bearer sada_live_sk_…
Content-Type: application/json

{
  "from": "customer@acme-corp.com",
  "to": "agent@yourdomain.com",
  "subject": "Re: Vendor Agreement Clarification",
  "html": "<p>We accept the revised indemnification clause in Section 4.</p><blockquote>On Oct 24, agent wrote:...</blockquote>"
}

200 OK
{
  "ok": true,
  "quarantined": false,
  "from": "customer@acme-corp.com",
  "to": ["agent@yourdomain.com"],
  "subject": "Re: Vendor Agreement Clarification",
  "thread": {
    "threadId": "th_a89f21dc",
    "isReply": true,
    "depth": 2
  },
  "content": {
    "cleanMarkdown": "We accept the revised indemnification clause in Section 4.",
    "cleanText": "We accept the revised indemnification clause in Section 4.",
    "tokenCountApprox": 12,
    "strippedSections": ["quoted_history_chain"]
  },
  "security": {
    "riskScore": 0.05,
    "threatLevel": "low",
    "quarantineRecommended": false,
    "detectedPatterns": []
  }
}

Domains, keys, webhooks

EndpointDoes
GET /emailsFilter dispatches by timeframe (?from, ?to), recipient (?q), tag, status, channel (?channel=http|smtp|mcp), or agent name. Cursor-based pagination. Scopes: messages:read or full_access
POST /emailsSingle send. Returns message ID, status, and job ID. Supports dry_run and scheduled delivery. Scopes: send or full_access
POST /emails/batchUp to 100 sends in one HTTP roundtrip with per-item idempotency keys. Scopes: send or full_access
GET /emails/:idDelivery timeline, latency breakdown, ISP disposition, headers, and metadata. Scopes: messages:read or full_access
DELETE /emails/:idCancel a queued, scheduled, or held email before dispatch. Scopes: messages:write or full_access
POST /emails/:id/resendRe-dispatch a previously completed or failed email. Role: owner or admin. Scopes: send or full_access
GET /accountAccount plan tier, monthly email quota, domain/seat utilization, reputation level, and retention days
GET /account/profileRead organization profile, logo, notification email, and communication preferences
PATCH /account/profileUpdate organization profile details, avatar URL, and technical notification preferences
PATCH /accountUpdate organization name, toggle open/click tracking, or cancel scheduled account deletion. Role: owner or admin
DELETE /accountSchedule account deletion with grace-period cancellation window. Role: owner only
GET /account/circuit-breakersQuery automated deliverability safety circuit breaker trip statuses for bounce/complaint protection
POST /account/circuit-breakers/resetReset tripped safety circuit breakers following root cause resolution. Role: owner or admin
GET /account/volumeSparkline volume history array over a window up to 90 days (default ?window=14d)
GET /account/statsSends, deliveries, bounce rate and complaint rate. ?provenance=true adds byChannel, bySource, and topAgents matrices; ?by_tag=true splits per tag; ?bounces=true splits bounce kinds; ?engagement=true adds open/click rates
POST /domainsRegister sending domain and generate 2048-bit DKIM keypair with DNS records. Role: owner or admin
GET /domainsList registered sending domains and their DNS verification statuses
GET /domains/:id/recordsFetch required SPF, DKIM, DMARC, and MX DNS records for a domain
POST /domains/:id/verifyLive DNS lookup with per-record pass or fail verdict and instructional guidance
GET /domains/historyDeleted domain history with preserved DKIM records for 1-click restore within retention window
POST /domains/history/:id/restoreRestore a previously removed domain without generating new DNS keys. Role: owner or admin
DELETE /domains/:idSafely delete a custom domain from the account. Role: owner or admin
GET/POST/PATCH/DELETE /keysList, create, update, or revoke scoped API keys (scopes, rate limit, recipient allowlist, CIDR IP allowlist, expiry, agent persona). Key creation requires OTP step-up challenge
POST /keys/otp/requestRequest a one-time passcode for key generation or secret reveal
GET /keys/approvalsRead sends held by an approval-mode API key for human verification. Scopes: approvals:read
POST /keys/approvals/:idApprove or reject an individual held send by message ID ({ decision: "approve" | "reject" }). Role: owner or admin
POST /mcpModel Context Protocol (MCP) JSON-RPC 2.0 streamable endpoint with 12 native tools
GET/POST/DELETE /integrations/slackConfigure or disconnect Slack 1-Click Interactive Approvals incoming webhook and signing secret. Role: owner or admin
POST /integrations/slack/testDispatch a live Block Kit test card to configured Slack channel to verify webhook connectivity. Role: owner or admin
POST /webhooks/slack/actionsSlack interactive callback endpoint processing 1-click Approve & Send / Reject button actions with HMAC verification
GET/POST/PATCH/DELETE /webhooksManage signed event delivery endpoints. Role: owner or admin
POST /webhooks/:id/testDispatch a synthetic test webhook event to verify signature verification. Role: owner or admin
POST /webhooks/:id/rotate-secretRotate the HMAC signing secret for a webhook endpoint. Role: owner or admin
POST /webhooks/simulateLive webhook delivery simulator to local developer endpoints (http://localhost:PORT) with HMAC verification
GET /webhooks/:id/deliveriesEvery webhook attempt: status, HTTP response code, error detail, and duration per event
POST /webhooks/:id/replayReplay historical webhook events to the destination URL. Role: owner or admin
GET /webhooks/dlqDead letter queue of failed deliveries with pagination (?limit, ?offset) and status filters (?status=dead|retried|discarded)
GET /webhooks/dlq/:idInspect individual dead letter delivery failure details, error payload, and timestamp
POST /webhooks/dlq/:id/retryRe-attempt dispatch of a failed dead-letter webhook event. Role: owner or admin
DELETE /webhooks/dlq/:idDiscard an irrecoverable dead letter delivery from the queue. Role: owner or admin
GET/POST/PATCH/DELETE /templatesVersioned Liquid email templates with rollback support. Role: owner or admin for writes
POST /templates/:id/renderRender a stored Liquid template against sample variables without sending
POST /templates/:id/testDispatch test send with custom JSON variables to verified operator inbox
GET/POST/DELETE /suppressionsRead, add, or remove suppressed recipients (?reason, ?q, ?limit, ?offset). Removal is audited. Role: owner or admin for writes
POST /suppressions (import)One address per call. The dashboard importer reads a CSV and submits each address this way, reporting any it refuses. Role: owner or admin
GET/POST /teamList team members or invite new team member with role. Role: owner or admin
PATCH/DELETE /team/members/:idUpdate team member role or remove member from organization. Role: owner only for role escalation
DELETE /team/invitations/:idRevoke a pending team invitation. Role: owner or admin
GET/POST /support/ticketsRaise a ticket and read support threads, with diagnostic app telemetry captured
POST /support/tickets/:id/messagesReply to an existing support ticket thread
POST /billing/checkoutCreate a Paddle subscription checkout session for a plan tier. Role: owner or admin
POST /billing/credits/checkoutPurchase one-time prepaid sending or verification credit packs. Role: owner or admin
POST /billing/portalGenerate an authenticated Paddle customer billing portal session URL. Role: owner or admin
POST /billing/cancelSchedule subscription cancellation at current billing period end. Role: owner only
POST /billing/resumeResume an active subscription scheduled for cancellation. Role: owner only
POST /tools/:checkSPF, DKIM, DMARC, MX, blocklist, and disposable email detection. No authentication required
POST /tools/utmNormalize and inject UTM campaign parameters into target URLs preserving query params and anchors
POST /tools/verifySingle address verification (RFC 5322 syntax, DNS MX server resolution, 60,000+ burner detection, typo autocorrect)
POST /tools/verify/batchMulti-address batch verification with CSV export and deliverability status tags
GET /arbiter/recipients/:recipient/statusQuery recipient cooldown status, active support ticket hold, and send velocity
POST /arbiter/recipients/:recipient/cooldownSet sliding-window contact cooldown (?duration=24h, priority, agentName) preventing multi-agent collisions
DELETE /arbiter/recipients/:recipient/cooldownClear active contact cooldown for a recipient. Role: owner or admin
POST /arbiter/ticketsRegister active customer support ticket hold (ticketId, recipient, subject, priorityThreshold) pausing automated outreach
DELETE /arbiter/tickets/:recipientResolve customer support hold, re-enabling agent outreach. Role: owner or admin
GET /arbiter/statsAccount-level collision statistics, active cooldown count, and prevented email blasts
POST /forms/submitSubmit public website form inquiry with invisible honeypot spam shield and Cloudflare Turnstile token validation
GET/POST/PATCH/DELETE /formsManage contact form endpoints, custom redirect URLs, and automated responder templates
GET /forms/:id/submissionsList received form submissions with pagination, contact metadata, and spam verdict
DELETE /forms/:id/submissions/:submissionIdDelete individual form submission. Role: owner or admin
POST /inboxes/ephemeralAllocate a short-lived agent test inbox (default domain auth.sadasend.com) with 15-minute auto-expiry
GET /inboxesList active testing mailboxes and message counts
GET /inboxes/:id/messagesRetrieve emails delivered to ephemeral inbox with HTML/text bodies and attachments
GET /inboxes/:id/otpInstant regex extraction of 6-digit verification code from latest received message
GET /inboxes/:id/streamServer-Sent Events (SSE) live push stream for incoming messages
POST /testing/wait-for-codeWait for and extract 6-digit OTP verification codes or magic links in sub-150ms for automated test suites
DELETE /inboxes/:idExplicitly tear down ephemeral inbox and purge received message bodies from memory