Verify a domain

Verify a domain

POST/api/v1/email/domains/{id}/verify

POST /email/domains/{id}/verify
curl -X POST 'https://www.unitpost.com/api/v1/email/domains/dom_123/verify' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'User-Agent: my-app/1.0'
Response · 200
{
  "object": "domain",
  "id": "id_123",
  "name": "Example",
  "status": "pending",
  "records": [
    {
      "type": "string",
      "name": "Example",
      "value": "string",
      "priority": 0
    }
  ],
  "dkim_selector": "string",
  "open_tracking": false,
  "click_tracking": false,
  "tls": "opportunistic",
  "tracking_subdomain": "string",
  "tracking_verified_at": "2026-01-01T00:00:00.000Z",
  "capabilities": {
    "sending": "enabled",
    "receiving": "enabled"
  },
  "receiving": {
    "status": "disabled",
    "record": {
      "type": "string",
      "name": "Example",
      "value": "string",
      "priority": 0
    },
    "checks": {
      "mx_found": false,
      "mx_lowest_priority": false,
      "other_mx_found": false
    },
    "checked_at": "2026-01-01T00:00:00.000Z"
  },
  "verified_at": "2026-01-01T00:00:00.000Z",
  "created_at": "2026-01-01T00:00:00.000Z",
  "updated_at": "2026-01-01T00:00:00.000Z",
  "checks": [
    "string"
  ]
}

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. With receiving on (capabilities.receiving), it also checks the receiving MX record and reports it in receiving. Requires the domains:write capability.

Parameters1 field
FieldTypeDescription
idrequiredstring · path—
Response · 200 fields17 fields
FieldTypeDescription
objectrequiredstring—
idrequiredstring—
namerequiredstring—
statusrequiredenumpending | verifying | verified | degraded | failed—
recordsrequiredobject[] | null—
dkim_selectorrequiredstring | null—
open_trackingrequiredboolean | null—
click_trackingrequiredboolean | null—
tlsrequiredenumopportunistic | enforced—
tracking_subdomainrequiredstring | null—
tracking_verified_atrequiredstring | nullWhen 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.
capabilitiesrequiredobject—
receivingrequiredobjectReceiving setup: the MX record to publish and the last check of it.
verified_atrequiredstring | null—
created_atrequiredstring—
updated_atrequiredstring—
checksobject[]—
200401404409502

Search docs and guides

Search the docs and product guides.