Overview

The DeliverSight API does one job: run a deliverability test from your own systems and read the result back. You create a test, send a message to the address you get, and fetch the score.

Everything else DeliverSight does — DMARC aggregation, domain monitoring, team and billing management — lives in the dashboard. The API is not a second interface to the product; it is the part worth automating.

Base URL

https://api.deliversight.com

All paths are versioned. Everything below is /v1.

It is small on purpose

There are six endpoints. That is not an early cut of a bigger API — it is the surface, and the deployment that serves it registers nothing else, so an endpoint you cannot find here does not exist publicly.

We would rather document six endpoints honestly than publish a generated schema of a hundred and leave you to discover which ones your key can actually call.

What v1 promises

While /v1 exists:

• Endpoints will not be removed, and their required parameters will not change.
• Response fields will not be removed or change type. New fields may be added, so parse leniently and ignore what you do not recognise.
• New event types may appear on webhooks. Handle unknown type values by ignoring them rather than failing.

If we ever need to break one of those, it will be /v2, and /v1 will keep working while you migrate.

What you need

An API key, created in the dashboard under API keys, on a plan that includes API access. Keys are scoped and belong to an account, not to you personally — see Authentication.

Where to start

The quickstart is the whole loop end to end, as a script you can paste. If you are integrating webhooks, read Webhooks carefully — the signature verification section in particular, since getting that wrong is the one mistake here with security consequences.