Skip to main content
POST
Email Compliance

Overview

Email Compliance answers one question: may I cold-email this address, and under whose law? It resolves an email to the most likely jurisdiction, returns that jurisdiction’s rule and recommendation, and tells you how much to trust the attribution. The verdict can arrive in two phases. Most checks resolve inside the request; a deeper attribution check may still be running when the first response returns. In that case the response carries pending and a provisional verdict, and the result is finalised shortly after - subscribe to realtime events to be notified when it settles.

Authentication

Requires an API key in the Authorization header.

Request

string
required
The email address to place under a jurisdiction.

Example request

Response

Unlike the older email endpoints, this route always returns the {success, result, message} envelope - including on validation and method errors. The HTTP status is real; a 200 never carries success: false.
boolean
Whether the lookup succeeded.
string
A sentence written for your end user. It already reflects whether the verdict is provisional, confident, or unknown - render it as-is rather than composing your own from the fields.
object
The applicable jurisdiction and its cold-email rule.

confidence drives the presentation

unknown is a deliberate answer, not a failure - the response is still 200 with a usable restrictive recommendation. Treating it as an error is the most common way to get this integration wrong.

Errors

Every response - including errors - uses the envelope, with a stable code in result.code.

Credits

Each lookup costs 1 credit, with free repeats inside the billing window. A repeat that finalises a previously provisional verdict is not charged again. See Credits.