Skip to content

Questions · Published 2026-09-23 · Updated 2026-11-07 · AgentiSend

What does domain_not_verified mean?

domain_not_verified means this sending domain is not verified, and the send was refused. The fix is on the error catalogue and names GET /domains/{id}, POST /domains, and POST /domains/{id}/verify.

domain_not_verified means this sending domain is not verified. The message in the error catalogue is "This sending domain is not verified." The send was refused. The catalogue fix names three situations: the domain is pending, it is not registered, or it failed.

Setting Message-ID, List-Unsubscribe, or List-Unsubscribe-Post when the From domain is not verified is the same code, and the message names the header. error.code in the response body is domain_not_verified. The onboarding sender cannot carry those headers: that refusal is invalid_parameter, and the message says the header cannot be set on the onboarding sender.

What the fix tells you to call

If it is pending, publish the required records from GET /domains/{id}. The same fix says checks continue on their own, and that you can test now by sending to an address ending in @simulator.agentisend.com. If it is not registered, POST /domains first. If it failed, GET /domains/{id} names the record to fix, then POST /domains/{id}/verify reopens the window. The hours in that window are the ones the catalogue sentence states.

GET /domains/{id}/setup is the sheet you paste: host, type, value, priority, required, and for a TXT the value_strings. A new domain sends once the required rows resolve. Domains and DNS names those rows.

curl -sS -X GET https://api.agentisend.com/domains/9c8f8f0e-3d1a-4d3f-9a1e-2b7c1a0f5e42 \
  -H "Authorization: Bearer $AGENTISEND_API_KEY"
200
{
  "capabilities": {
    "receiving": "enabled",
    "sending": "enabled"
  },
  "click_tracking": false,
  "created_at": "2026-09-04T09:14:00.000Z",
  "dkim_selector": "example",
  "id": "9c8f8f0e-3d1a-4d3f-9a1e-2b7c1a0f5e42",
  "inbound_hold_mode": "monitor",
  "inbound_policy": "open",
  "inbound_refused_count": -9007199254740991,
  "name": "example",
  "object": "domain",
  "open_tracking": false,
  "provider_hints": {
    "cloudflare": "example",
    "godaddy": "example",
    "namecheap": "example",
    "route53": "example"
  },
  "recent_events": [],
  "records": [],
  "region": "us",
  "return_path_subdomain": "example",
  "status": "pending",
  "tls_mode": "opportunistic",
  "tracking_issues": [],
  "tracking_subdomain": "example",
  "verified_at": "2026-09-04T09:14:00.000Z",
  "warnings": [],
  "zone": "example"
}
Response

Where to publish them

One page per DNS host, with that host's own dashboard steps:

Next