Update a domain

PATCH/api/v1/email/domains/{id}

PATCH /email/domains/{id}

curl -X PATCH 'https://www.unitpost.com/api/v1/email/domains/dom_123' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'User-Agent: my-app/1.0' \
  -H 'Content-Type: application/json' \
  -d '{
    "click_tracking": true,
    "open_tracking": true
  }'

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",
  "verified_at": "2026-01-01T00:00:00.000Z",
  "created_at": "2026-01-01T00:00:00.000Z",
  "updated_at": "2026-01-01T00:00:00.000Z"
}

Update a domain's sending options: open/click tracking defaults, TLS enforcement, and the tracking subdomain. These act as the domain-level defaults that individual emails and campaigns can override (see Update a campaign). Requires the domains:write capability.

Parameters1 field

Field	Type	Description
`id`required	string · path	—

Request body4 fields

Field	Type	Description
`open_tracking`	object	—
`click_tracking`	object	—
`tls`	enumopportunistic \| enforced	—
`tracking_subdomain`	object	—

Response · 200 fields14 fields

Field	Type	Description
`object`required	string	—
`id`required	string	—
`name`required	string	—
`status`required	enumpending \| verifying \| verified \| degraded \| failed	—
`records`required	object	—
`dkim_selector`required	object	—
`open_tracking`required	object	—
`click_tracking`required	object	—
`tls`required	enumopportunistic \| enforced	—
`tracking_subdomain`required	object	—
`tracking_verified_at`required	object	—
`verified_at`required	object	—
`created_at`required	string	—
`updated_at`required	string	—

200401404422

Update a domain

Update a domain

Search docs and guides