Domains

Verify a domain

Run an on-demand DNS check and advance the domain's verification status. The response includes per-record checks so you can see exactly which DNS records are still missing or wrong. checks.mx and checks.spf are true once the record is correct on your nameservers; checks.dkim also needs the email provider to confirm the key. The domain is verified when all three are true. Get the records to publish from Retrieve a domain. Verification also re-runs periodically in the background. If another workspace also added this domain, yours verifies only once the domain's sending identity is yours: your DKIM record is live and theirs is gone on two checks at least 10 minutes apart, or their domain is deleted. While they have it verified, this returns 409 once all your records are live, and nothing is written. Requires the domains:write capability.

post/email/domains/{id}/verify

Request

  • Base URL: https://www.unitpost.com/api/v1
  • URL: https://www.unitpost.com/api/v1/email/domains/{id}/verify
  • Auth: HTTP bearer

Response

The updated domain with per-record checks.

object'domain' required
idstring required
namestring required
status'pending' | 'verifying' | 'verified' | 'degraded' | 'failed' required
dkim_selectorstring nullable required
open_trackingboolean nullable required
click_trackingboolean nullable required
tls'opportunistic' | 'enforced' required
tracking_subdomainstring nullable required
tracking_verified_atstring nullable required

When tracked links and open pixels started using the custom tracking host (tracking_subdomain). Non-null only while sends actually use it: the domain is verified (or degraded) and the host's last check proved it answers over HTTPS. Otherwise null, and links use the default tracking host. A host that stops answering, or a domain that's no longer verified, goes back to null.

verified_atstring nullable required
created_atstring required
updated_atstring required

Changes

No recorded changes to this operation across all 1 revision of this API.