Email Monitoring API — Email Posture as JSON

Email monitoring API: turn your email posture into JSON, on demand. ToolTrusted has a read-only REST API so developers and platform teams can pull the same deterministic intelligence the dashboard shows — domains, dashboards, incidents, trends, analytics, recommendations and benchmarks — straight into their own systems.

It works as an email deliverability API and a real-time email health API: point it at any domain and get its posture as JSON, with DMARC API integration and email infrastructure webhooks so changes push straight to your stack.

The email monitoring API returns the same posture and Health Score you see in the dashboard, as clean JSON. Point it at any domain, schedule it from your own stack, and pipe results into webhooks and Slack alerts or a public status page.

Who the email monitoring API is for

Developers and platform teams who want email-infrastructure intelligence wired into their stack — a status dashboard, an internal tool, a scheduled job, a CI check. The API returns the exact read-models behind the product, so there’s no second source of truth to reconcile. Pair it with Automation (webhooks & Slack) to both pull posture and be pushed changes.

Authentication

Each request is authenticated with a per-workspace API key, sent as an HTTP Bearer token (RFC 6750) header — never a query string. Keys are generated in your Workspace and shown once; you can hold several named keys for different integrations and revoke any of them. Organization owners get org-scoped keys that read the whole portfolio.

# Send your key as a Bearer token (or the X-TT-Api-Key header)
curl https://tooltrusted.com/wp-json/tooltrusted/v1/api/dashboard \
  -H "Authorization: Bearer ttk_<workspace>_<secret>"

# Every response uses a stable envelope
{ "ok": true, "data": { ... }, "meta": { "generated_at": "..." } }

Every response from the email monitoring API is deterministic: the same domain returns the same posture and the same Health Score, so you can diff two runs and alert only on real change. Because it reads public DNS and posture only, there is nothing to install and no agent to run, so it is safe to poll on a schedule from CI, a cron job or a serverless function.

email monitoring api request and webhook payload architecture
Email monitoring API: a GET request returns a JSON status payload; webhooks push events on change.

Endpoints

EndpointReturns
GET /api/domainsYour domains and their latest score/grade.
GET /api/dashboardYour workspace verdict, counts and priority list.
GET /api/incidentsOpen and recent incidents across your domains.
GET /api/domains/<id>/timelineThe event story for one domain.
GET /api/domains/<id>/trendsSignal trends over the window.
GET /api/domains/<id>/analyticsMTTR, recurring/flapping, reliability verdict.
GET /api/domains/<id>/incidentsIncident lifecycles for one domain.
GET /api/domains/<id>/recommendationsImpact-ranked fixes for one domain.
GET /api/domains/<id>/benchmarkHow the domain compares to the population.
GET /api/domains/<id>/snapshotThe latest measured posture.
GET /api/org/dashboard, /api/org/workspacesPortfolio rollup (owner key).
GET /api/public-status/<id>/<sig>Public, PII-free status — no key required.
Deterministic and versioned. Every response is a pure projection over your immutable history, so the same request gives the same answer; the read-model DTOs carry their own schema_version. Requests are rate-limited, errors use a consistent { ok: false, error: { code, message } } shape, and the public-status endpoint returns only public-safe data (no emails, no internal ids).

Which plan includes this

Pro · $29/mo
The authenticated API is part of Pro (the public-status endpoint is a signed, PII-free share link available on every plan). It is independent and deterministic — measured signals only, no fabricated fields, and no claim to measure inbox placement. See plans →

Start building