Register domain for verification

Deprecated

POST

/v1/domains

curl --request POST \
  --url https://api.mailerdash.com/v1/domains \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{ "domain": "mycompany.com" }'

• Production
• Local development

DEPRECATED — use the dashboard domain-centric flow (POST /v1/client/domains then POST /v1/client/domains/{domain}/verify), which manages the account-level domain (ownership + verification, the source of truth for send authorization). This key-scoped endpoint still works and now also writes the account-level domain, but the domain-centric endpoints are the supported path. Starts domain ownership verification. Returns TXT record to add to DNS.

Authorizations

• BearerAuth

Request Body ^required

Media type application/json

object

domain

required

string

Example

mycompany.com

Responses

201

Domain registered — add TXT record then call /verify

Media type application/json

object

domain

string

token

string

instructions

object

record_type

string

record_name

string

record_value

string

next_step

string

Example

{
  "instructions": {
    "record_type": "TXT",
    "record_name": "_md-verify.mycompany.com",
    "record_value": "md-verify=abc123"
  }
}

400

Invalid domain

401

Unauthorized

409

Domain already registered. error.code distinguishes the cases: domain_held_by_hosting_tenant when the domain is registered to your own mailbox-hosting service (contact support to link it to this account as well — self-service cannot, because it would inherit the tenant’s verified state), otherwise a generic conflict when another account holds it.