Quickstart

1. Get a key#

Sign in at app.stormdoor.dev and create a key from the console. Keys look like sk_live_... and are shown once, at creation time — store it somewhere your server can read, not in client-side code (see authentication for why).

2. Make a call#

Every gate is a POST with a JSON body and a Bearer token:

curl -X POST https://api.stormdoor.dev/v1/emails \
  -H "Authorization: Bearer sk_live_..." \
  -H "content-type: application/json" \
  -d '{"email":"bob@gmail.com"}'

3. Read the verdict#

Every gate returns the same shape. verdict is the one field to branch on first:

• "clean" — no findings. Nothing to act on.
• "suspect" — at least one low- or medium-severity finding. Worth a second look, not necessarily a block.
• "block" — at least one high- or critical-severity finding.

The full shape — findings, data, checks_run, checks_skipped — is covered on the response format page. Each gate's own page (emails, domains, links) has a real example response and the full list of checks it runs.

4. Handle failure#

A call can fail outright — rate limited, out of credits, a transient error. Read errors & fail-open before you wire this into a live signup form: this API is built to fail open, and your integration should decide what that means for you rather than discovering it during an outage.