PUT
Record a verification outcome for a sending domain

Authorizations

Authorization
string
header
required

A secret API key. Publishable keys cannot reach this API. A key may carry an expiry, and an expired key is refused exactly like an unknown one, with a 401 that names no reason; check the key's expires_at in the dashboard rather than inferring it from a response. When a merchant rolls a key's secret they choose a grace window of up to 3 days, and for its duration BOTH the new secret and the one it replaced authenticate, so an integration moves over on its own deploy schedule instead of at the instant the button is pressed. Move before the window closes: after it, the old secret is refused. Nothing else about this contract moves with a roll. The key keeps its id and its scopes, so the only thing an integration updates is the credential itself.

Headers

Idempotency-Key
string
required

A unique key per logical write. Replaying a request with the same key returns the first response byte for byte instead of applying the write twice.

Path Parameters

domain
string
required

Body

application/json

ONE FIELD, and the narrowness is the contract. dkim_record is refused by name on this route: the admin surface writes both columns together, and a key able to set the record could put an attacker's signing key in front of the merchant, who would publish it in real DNS. No precondition is required. The route writes a single field, so the only thing a race can lose is a status two callers disagree about, which the next read shows and the next write corrects.

status
enum<string>
required

What the provider says about this domain now. Nothing on this platform gates a send on it: it is the merchant's record of their own DNS.

Available options:
pending,
verified,
failed

Response

Success

data
object