Runs examples for real against your account. Test keys only; kept in this tab, never stored on our side. Get a key
ZapSMTP / Docs / Inbound setup

Verify MX records

POST/v1/inbound/domains/{id}/verify

Check the domain's MX record now.

Requires a full-access live key; test keys get 403 test_key_restricted.

mx_verified becomes true as soon as any MX record of the domain points to our inbound host.

Path parameters

idstring (UUID)required
Inbound domain id

Errors

restricted_api_keyHTTP 403
test_key_restrictedHTTP 403
test-mode keys can send test email and read, not change the account: use a live key
not_foundHTTP 404
inbound domain not found
POST/v1/inbound/domains/{id}/verify
curl -X POST 'https://zapsmtp.xyz/v1/inbound/domains/019a1e9b-41c2-7a0e-b5d1-3f6c2e8a9d47/verify' \
  -H "Authorization: Bearer $ZAP_API_KEY"
Set ZAP_API_KEY in your environment.
Response 200 OK
{
  "domain": {
    "id": "019a1f21-5d6e-7f80-9a1b-2c3d4e5f6a7b",
    "name": "reply.acme.com",
    "managed": false,
    "reject_spam": true,
    "mx_verified": true,
    "last_checked_at": "2026-10-21T15:05:00Z",
    "created_at": "2026-10-20T11:30:00Z",
    "records": [
      {
        "record": "MX",
        "type": "MX",
        "name": "reply.acme.com",
        "value": "10 zapsmtp.xyz",
        "required": true,
        "status": "verified"
      }
    ],
    "example_address": "anything@reply.acme.com"
  },
  "mx_found": [
    "zapsmtp.xyz"
  ]
}