User Sender Domain API Documentation

User-area sender domain management endpoints for creating, listing, retrieving, updating, deleting, verifying, and inspecting the DNS records of from-address domains owned by the authenticated user.

These are the user-owned, list-bound sender domains visible at /app/user/senderdomains/, with per-domain DNS records (CNAME / A / MX / TXT) for SPF/DMARC, an MFROM/return-path subdomain, an optional tracking subdomain, and a verification flow that performs live DNS lookups. They are distinct from the email-gateway delivery domains managed via the emailgateway.*domain* endpoints, and from the admin-only sender.domains endpoint, which returns a flat cross-tenant dump used for PowerMTA provisioning.

List User Sender Domains

GET /api/v1/user.senderdomains

API Usage Notes

Authentication required: User API Key
Required permissions: User.Update
Rate limit: 100 requests per 60 seconds
Legacy endpoint access via /api.php is also supported

Returns only user-owned, addressable sender domains. The synthetic group-default sender domain (DomainID=0) that the model normally prepends is intentionally excluded — every entry in the response has a real DomainID and is valid for Get / Update / Delete / Verify / DNS.

Request Body Parameters:

Parameter	Type	Required	Description
Command	String	Yes	API command: `user.senderdomain.list`
SessionID	String	No	Session ID obtained from login
APIKey	String	No	API key for authentication

Example RequestSuccess ResponseError ResponseError Codes

bash

curl -X GET "https://example.com/api/v1/user.senderdomains?APIKey=your-api-key"

json

{
  "Success": true,
  "SenderDomains": [
    {
      "DomainID": "12",
      "SenderDomain": "example.com",
      "UserID": "1",
      "CreatedAt": "2026-04-25 22:54:00",
      "Status": "Enabled",
      "LastVerifiedAt": "2026-05-23 09:11:00",
      "VerificationMeta": {
        "DNSRecords": {
          "sl.example.com": ["CNAME", "tracking-host.octeth.example.", true]
        }
      },
      "PolicyMeta": [],
      "Options": {
        "LinkTracking": 1,
        "OpenTracking": 1,
        "UnsubscribeLink": 0,
        "CustomSubdomain": "sl",
        "CustomTrackPrefix": "track",
        "TrackPrefixDisabled": false
      },
      "Volume7d": 184320,
      "VolumeDelta": "+12%",
      "Reputation": 96,
      "ReputationBucket": "excellent",
      "DeliveryRate": 99.4,
      "BounceRate": 0.5
    }
  ]
}

Operational fields (issue #1889). The following fields are derived from oempro_sender_domain_stats / oempro_eg_domain_stats and are populated on every List and Get response:

Field	Type	Description
`LastVerifiedAt`	datetime / null	Updated on every `user.senderdomain.verify` call (regardless of pass/fail). `null` when the domain has never been verified.
`Volume7d`	integer	Total attributable sends in the last 7 days.
`VolumeDelta`	string / null	Trailing-7-day volume change vs the prior 7-day window — for example `"+12%"`, `"-3%"`, `"new"` (no prior-window data), or `null` (no current-window volume).
`Reputation`	integer / null	0–100 score over the last 30 days. `null` when there's no send volume to score.
`ReputationBucket`	string / null	One of `excellent` (≥90), `good` (≥70), `fair` (≥50), `poor`. `null` when `Reputation` is `null`.
`DeliveryRate`	float / null	Last-30-day delivery percentage. Falls back to `(Sent − Bounced − Complaints) / Sent` when explicit `Delivered` events aren't recorded for the period (non-PMTA installs).
`BounceRate`	float / null	Last-30-day bounce percentage.

json

{
  "Errors": [
    {
      "Code": 0,
      "Message": "Authentication failed"
    }
  ]
}

txt

(none — this endpoint has no business-logic error codes; an empty result returns SenderDomains: [])

Get a Sender Domain

GET /api/v1/user.senderdomain

API Usage Notes

Authentication required: User API Key
Required permissions: User.Update
Rate limit: 100 requests per 60 seconds
Legacy endpoint access via /api.php is also supported

Request Body Parameters:

Parameter	Type	Required	Description
Command	String	Yes	API command: `user.senderdomain.get`
SessionID	String	No	Session ID obtained from login
APIKey	String	No	API key for authentication
DomainID	Integer	Yes	The ID of the sender domain to retrieve. Must be owned by the calling user
days	Integer	No	When present, the response also includes a `Stats` map keyed by `Y-m-d` covering the last N days of per-domain activity. Clamped to `1..365` (default `30`). Mirrors `user.webhook.stats`.

The same operational fields documented under List User Sender Domains (LastVerifiedAt, Volume7d, VolumeDelta, Reputation, ReputationBucket, DeliveryRate, BounceRate) are returned on every Get response regardless of whether days is supplied.

bash

curl -X GET "https://example.com/api/v1/user.senderdomain?APIKey=your-api-key&DomainID=12"

bash

curl -X GET "https://example.com/api/v1/user.senderdomain?APIKey=your-api-key&DomainID=12&days=30"

json

{
  "Success": true,
  "SenderDomain": {
    "DomainID": "12",
    "SenderDomain": "example.com",
    "UserID": "1",
    "CreatedAt": "2026-04-25 22:54:00",
    "Status": "Enabled",
    "LastVerifiedAt": "2026-05-23 09:11:00",
    "VerificationMeta": {
      "DNSRecords": {
        "sl.example.com": ["CNAME", "tracking-host.octeth.example.", true]
      }
    },
    "PolicyMeta": [],
    "Options": {
      "LinkTracking": 1,
      "OpenTracking": 1,
      "UnsubscribeLink": 0,
      "CustomSubdomain": "sl",
      "CustomTrackPrefix": "track",
      "TrackPrefixDisabled": false
    },
    "Volume7d": 184320,
    "VolumeDelta": "+12%",
    "Reputation": 96,
    "ReputationBucket": "excellent",
    "DeliveryRate": 99.4,
    "BounceRate": 0.5
  }
}

json

{
  "Success": true,
  "SenderDomain": { /* same shape as above */ },
  "Days": 30,
  "Stats": {
    "2026-05-23": { "Period": "2026-05-23", "Sent": 12000, "Delivered": 11940, "Bounced": 60, "Complaints": 0 },
    "2026-05-22": { "Period": "2026-05-22", "Sent": 11820, "Delivered": 11760, "Bounced": 58, "Complaints": 2 }
  }
}

json

{
  "Errors": [
    {
      "Code": 2,
      "Message": "Sender domain not found"
    }
  ]
}

txt

1: Missing DomainID parameter
2: Sender domain not found (also returned when the domain exists but is owned by another user — to avoid leaking ownership)

Days with no recorded activity are omitted from Stats rather than zero-filled — callers that need a full window should pad client-side.

Create a Sender Domain

POST /api/v1/user.senderdomain

API Usage Notes

Authentication required: User API Key
Required permissions: User.Update
Rate limit: 100 requests per 60 seconds
Legacy endpoint access via /api.php is also supported

The new domain starts in Status='Approval Pending'. The response includes the auto-generated VerificationMeta.DNSRecords array — these are the CNAME / A / MX / TXT records the user must add to their DNS zone before the domain can be verified.

If a (SenderDomain, UserID) pair already exists (e.g. it was previously soft-deleted), the model uses ON DUPLICATE KEY UPDATE to refresh the row's Status to Approval Pending rather than failing.

Request Body Parameters:

Parameter	Type	Required	Description
Command	String	Yes	API command: `user.senderdomain.create`
SessionID	String	No	Session ID obtained from login
APIKey	String	No	API key for authentication
SenderDomain	String	Yes	The domain name to register (e.g. `example.com`). Cannot be `localhost`
LinkTracking	Boolean	No	Whether to enable click tracking on links sent from this domain. Default: `true`
OpenTracking	Boolean	No	Whether to enable open tracking. Default: `true`
UnsubscribeLink	Boolean	No	Whether to inject the unsubscribe link automatically. Default: `false`
CustomSubdomain	String	No	Override the default MFROM/return-path subdomain. Letters, digits, and hyphens only; max 32 chars; no leading/trailing hyphens
CustomTrackPrefix	String	No	Override the default click-tracking subdomain prefix. Same character rules as `CustomSubdomain`

Example RequestSuccess ResponseError ResponseError Codes

bash

curl -X POST https://example.com/api/v1/user.senderdomain \
  -H "Content-Type: application/json" \
  -d '{
    "Command": "user.senderdomain.create",
    "APIKey": "your-api-key",
    "SenderDomain": "example.com",
    "LinkTracking": true,
    "OpenTracking": true,
    "UnsubscribeLink": false
  }'

json

{
  "Success": true,
  "DomainID": 12,
  "SenderDomain": {
    "DomainID": "12",
    "SenderDomain": "example.com",
    "UserID": "1",
    "CreatedAt": "2026-04-26 09:30:00",
    "Status": "Approval Pending",
    "VerificationMeta": {
      "DNSRecords": {
        "sl.example.com": ["CNAME", "tracking-host.octeth.example."],
        "track-sl.example.com": ["CNAME", "tracking-host.octeth.example."]
      }
    },
    "PolicyMeta": [],
    "Options": {
      "LinkTracking": 1,
      "OpenTracking": 1,
      "UnsubscribeLink": 0
    }
  }
}

json

{
  "Errors": [
    {
      "Code": 5,
      "Message": "Sender domain limit reached for your account"
    }
  ]
}

txt

1: Missing SenderDomain parameter
4: localhost is not a valid sender domain
5: Sender domain limit reached for your account (returned with HTTP 403)
6: Invalid CustomSubdomain or CustomTrackPrefix (letters, digits, and hyphens only; max 32 chars; no leading/trailing hyphens)
7: Sender domain create process failed (returned with HTTP 400)
8: Sender domain could not be retrieved after creation (returned with HTTP 500)

Update a Sender Domain

PATCH /api/v1/user.senderdomain

API Usage Notes

Authentication required: User API Key
Required permissions: User.Update
Rate limit: 100 requests per 60 seconds
Legacy endpoint access via /api.php is also supported
PATCH requests must send all parameters in a JSON body (Content-Type: application/json). The dispatcher does not parse query-string or form-encoded payloads for PATCH, so ?DomainID=... and ?APIKey=... will be ignored — include them in the JSON body alongside the other update fields.

This is a partial update. Only fields explicitly present in the request body are modified — omitted fields keep their currently stored value (the API does not reset them to defaults).

If the request changes any DNS-affecting field (CustomSubdomain, CustomTrackPrefix, or UseTrackingSubdomain / TrackPrefixDisabled), the server automatically:

Regenerates the VerificationMeta.DNSRecords template via RegenerateDNSRecords.
Resets Status to Approval Pending (the previous DNS verification is no longer valid for the new subdomain layout).
Invalidates the Redis verification cache for this domain.
Sets DnsRegenerated: true in the response so the caller knows DNS records changed.

The user must then update their DNS zone with the new records and call user.senderdomain.verify to re-verify.

Request Body Parameters:

Parameter	Type	Required	Description
Command	String	Yes	API command: `user.senderdomain.update`
SessionID	String	No	Session ID obtained from login
APIKey	String	No	API key for authentication
DomainID	Integer	Yes	The ID of the sender domain to update. Must be owned by the calling user
LinkTracking	Boolean	No	Toggle click tracking. Omitted: stored value preserved
OpenTracking	Boolean	No	Toggle open tracking. Omitted: stored value preserved
UnsubscribeLink	Boolean	No	Toggle automatic unsubscribe-link injection. Omitted: stored value preserved
UseTrackingSubdomain	Boolean	No	Whether to use a separate tracking subdomain. Internally stored as the inverse `TrackPrefixDisabled` flag
CustomSubdomain	String	No	New override for the MFROM/return-path subdomain. Letters, digits, and hyphens only; max 32 chars; no leading/trailing hyphens. Triggers DNS regeneration
CustomTrackPrefix	String	No	New override for the tracking subdomain prefix. Same character rules. Triggers DNS regeneration
status	String	No	Toggle the domain on/off. Accepts `Enabled` or `Disabled` (case-insensitive). `Approval Pending`, `Suspended`, `Deleted` are system-controlled and rejected (issue #1890)

Example RequestSuccess ResponseError ResponseError Codes

bash

curl -X PATCH https://example.com/api/v1/user.senderdomain \
  -H "Content-Type: application/json" \
  -d '{
    "Command": "user.senderdomain.update",
    "APIKey": "your-api-key",
    "DomainID": 12,
    "CustomSubdomain": "em",
    "UseTrackingSubdomain": true
  }'

json

{
  "Success": true,
  "DnsRegenerated": true,
  "SenderDomain": {
    "DomainID": "12",
    "SenderDomain": "example.com",
    "UserID": "1",
    "CreatedAt": "2026-04-25 22:54:00",
    "Status": "Approval Pending",
    "VerificationMeta": {
      "DNSRecords": {
        "em.example.com": ["CNAME", "tracking-host.octeth.example."],
        "track-em.example.com": ["CNAME", "tracking-host.octeth.example."]
      }
    },
    "PolicyMeta": [],
    "Options": {
      "LinkTracking": 1,
      "OpenTracking": 1,
      "UnsubscribeLink": 0,
      "CustomSubdomain": "em",
      "TrackPrefixDisabled": false
    }
  }
}

json

{
  "Errors": [
    {
      "Code": 6,
      "Message": "Invalid CustomSubdomain. Letters, digits, and hyphens only; max 32 chars; no leading/trailing hyphens"
    }
  ]
}

txt

1: Missing DomainID parameter
2: Sender domain not found (also returned when the domain exists but is owned by another user)
6: Invalid CustomSubdomain or CustomTrackPrefix (letters, digits, and hyphens only; max 32 chars; no leading/trailing hyphens)
7: Sender domain could not be retrieved after update (returned with HTTP 500)
9: Invalid Status value. Allowed: Enabled, Disabled (issue #1890)
10: Cannot enable an unverified domain — run user.senderdomain.verify first (issue #1890)

Pausing vs deleting (issue #1890)

A domain in Status='Disabled' keeps its DNS records and stats history, but is filtered out by the send-time resolver (SenderDomains::ResolveForEmail) — campaigns and journeys that reference a paused domain fall back to the group's default sender domain until the user flips it back to Enabled. The flip is single round-trip: no DNS re-verification, no Redis cache invalidation.

:::

Delete a Sender Domain

DELETE /api/v1/user.senderdomain

API Usage Notes

Authentication required: User API Key
Required permissions: User.Update
Rate limit: 100 requests per 60 seconds
Legacy endpoint access via /api.php is also supported

Soft delete — the row is not removed from the database. The model sets Status='Deleted' and fires the Delete.SenderDomain plugin hook so listeners can run cleanup logic (e.g., remove the domain from active campaigns). Subsequent Get / List calls will not return the domain.

Request Body Parameters:

Parameter	Type	Required	Description
Command	String	Yes	API command: `user.senderdomain.delete`
SessionID	String	No	Session ID obtained from login
APIKey	String	No	API key for authentication
DomainID	Integer	Yes	The ID of the sender domain to delete. Must be owned by the calling user

Example RequestSuccess ResponseError ResponseError Codes

bash

curl -X DELETE "https://example.com/api/v1/user.senderdomain?APIKey=your-api-key&DomainID=12"

json

{
  "Success": true
}

json

{
  "Errors": [
    {
      "Code": 2,
      "Message": "Sender domain not found"
    }
  ]
}

txt

1: Missing DomainID parameter
2: Sender domain not found (also returned when the domain exists but is owned by another user)

Verify a Sender Domain

POST /api/v1/user.senderdomain.verify

API Usage Notes

Authentication required: User API Key
Required permissions: User.Update
Rate limit: 100 requests per 60 seconds
Legacy endpoint access via /api.php is also supported

Performs a live DNS lookup for each expected record (CNAME / A / MX / TXT). Results are cached for 60 seconds in Redis to avoid hammering DNS resolvers — calling this endpoint twice in quick succession will return the same outcome.

The endpoint persists Status based on the result (mirrors what the UI's edit page does on every load):

All records resolve correctly → Status = 'Enabled'
Any record fails → Status = 'Approval Pending'

The latest per-record verified flags are merged into the existing VerificationMeta (other keys are preserved) so subsequent Get / DNS calls reflect the same state shown in the UI. The Status and VerificationMeta columns are only rewritten when the verified state actually changed, but LastVerifiedAt is always updated on every call (issue #1889) — this is what powers the "Checked X ago" subtitle in the sender-domain UI.

Request Body Parameters:

Parameter	Type	Required	Description
Command	String	Yes	API command: `user.senderdomain.verify`
SessionID	String	No	Session ID obtained from login
APIKey	String	No	API key for authentication
DomainID	Integer	Yes (single-domain mode)	The ID of the sender domain to verify. Must be owned by the calling user. Ignored when `verifyall=true`
verifyall	Boolean	No	When true, verifies every `Approval Pending` domain owned by the caller in one call (issue #1890). Capped at 25 domains per call; if more are pending, the response carries `Truncated: true` and the caller should re-invoke to process the next batch. `DomainID` is ignored when this is set

bash

curl -X POST https://example.com/api/v1/user.senderdomain.verify \
  -H "Content-Type: application/json" \
  -d '{
    "Command": "user.senderdomain.verify",
    "APIKey": "your-api-key",
    "DomainID": 12
  }'

bash

curl -X POST https://example.com/api/v1/user.senderdomain.verify \
  -H "Content-Type: application/json" \
  -d '{
    "Command": "user.senderdomain.verify",
    "APIKey": "your-api-key",
    "verifyall": true
  }'

json

{
  "Success": true,
  "DomainID": 12,
  "IsVerified": true,
  "Status": "Enabled",
  "DNSRecords": {
    "sl.example.com": ["CNAME", "tracking-host.octeth.example.", true],
    "track-sl.example.com": ["CNAME", "tracking-host.octeth.example.", true]
  }
}

json

{
  "Success": true,
  "VerifyAll": true,
  "Verified": 18,
  "Failed": 7,
  "Truncated": false,
  "Domains": [
    {"DomainID": 12, "IsVerified": true,  "Status": "Enabled"},
    {"DomainID": 13, "IsVerified": false, "Status": "Approval Pending"}
  ]
}

json

{
  "Errors": [
    {
      "Code": 2,
      "Message": "Sender domain not found"
    }
  ]
}

txt

1: Missing DomainID parameter (single-domain mode only; not raised when verifyall=true)
2: Sender domain not found (also returned when the domain exists but is owned by another user)

Bulk verify response shape (issue #1890)

The bulk path's per-domain entries intentionally omit DNSRecords to keep the payload compact on large accounts. Callers that need the full record list for a specific domain should follow up with user.senderdomain.dns or user.senderdomain.get. The 60-second Redis cache inside the per-domain probe still applies, so a bulk verify that runs shortly after a single-domain verify (or vice versa) reuses the cached probe rather than re-hitting DNS.

Get DNS Records for a Sender Domain

GET /api/v1/user.senderdomain.dns

API Usage Notes

Authentication required: User API Key
Required permissions: User.Update
Rate limit: 100 requests per 60 seconds
Legacy endpoint access via /api.php is also supported

Read-only. Returns the stored VerificationMeta.DNSRecords (the records the user needs to add to their DNS zone), normalized to a structured shape: { host: { Type, Value, IsVerified } }.

IsVerified is tri-state:

null — this record has never been probed (e.g. domain was just created or its subdomain settings just changed)
true — the last probe by user.senderdomain.verify matched the expected value
false — the last probe ran but did not match (DNS not configured yet, or misconfigured)

The records are kept fresh automatically — when Update changes a DNS-affecting setting, the server regenerates them. If the stored records are missing/empty (legacy or just-created edge case), this endpoint falls back to regenerating the template purely for display, without persisting.

Request Body Parameters:

Parameter	Type	Required	Description
Command	String	Yes	API command: `user.senderdomain.dns`
SessionID	String	No	Session ID obtained from login
APIKey	String	No	API key for authentication
DomainID	Integer	Yes	The ID of the sender domain. Must be owned by the calling user

Example RequestSuccess ResponseError ResponseError Codes

bash

curl -X GET "https://example.com/api/v1/user.senderdomain.dns?APIKey=your-api-key&DomainID=12"

json

{
  "Success": true,
  "DomainID": 12,
  "SenderDomain": "example.com",
  "DNSRecords": {
    "sl.example.com": {
      "Type": "CNAME",
      "Value": "tracking-host.octeth.example.",
      "IsVerified": true
    },
    "track-sl.example.com": {
      "Type": "CNAME",
      "Value": "tracking-host.octeth.example.",
      "IsVerified": null
    }
  }
}

json

{
  "Errors": [
    {
      "Code": 2,
      "Message": "Sender domain not found"
    }
  ]
}

txt

1: Missing DomainID parameter
2: Sender domain not found (also returned when the domain exists but is owned by another user)

Send a Test Email New in 5.9.x

POST /api/v1/user.senderdomain.sendtest

API Usage Notes

Authentication required: User API Key
Required permissions: User.Update
Rate limit: 10 requests per 5 minutes (stricter than the rest of the family — this dispatches real outbound mail)
Legacy endpoint access via /api.php is also supported
Not available in demo mode (returns HTTP 403 with code 99)

Sends a single synthetic test message from a specific sender domain so the user can confirm end-to-end deliverability before wiring the domain up to a real campaign or journey. The body renders the three artifacts that matter for sender-domain debugging: the resolved from-address (<from-prefix>@<SenderDomain>), the MFROM/return-path subdomain (SenderDomains::BuildMFROMDomain), and the tracking subdomain (SenderDomains::BuildTrackingDomain). If the recipient opens the message, the user can confirm those resolve correctly outside the campaign send path.

The dispatch goes through Emails::SendPreviewEmail (the same engine path as email.emailpreview and autoresponder.sendtest), so it honors the user's group SendMethod, transactional delivery server (if configured), and tracking domain rewriting.

Request Body Parameters:

Parameter	Type	Required	Description
Command	String	Yes	API command: `user.senderdomain.sendtest`
SessionID	String	No	Session ID obtained from login
APIKey	String	No	API key for authentication
DomainID	Integer	Yes	Sender domain to send from. Must be owned by the calling user
to	String	Yes	Recipient address. Any valid email; the 10/5min rate limit is the abuse control
subject	String	No	Override the default subject line. Defaults to `"Sender domain test from <SenderDomain>"`

Example RequestSuccess ResponseError ResponseError Codes

bash

curl -X POST https://example.com/api/v1/user.senderdomain.sendtest \
  -H "Content-Type: application/json" \
  -d '{
    "Command": "user.senderdomain.sendtest",
    "APIKey": "your-api-key",
    "DomainID": 12,
    "to": "ops@example.com"
  }'

json

{
  "Success": true,
  "DomainID": 12,
  "SenderDomain": "example.com",
  "To": "ops@example.com",
  "Subject": "Sender domain test from example.com",
  "MessageID": "senderdomaintest_6644a1b2c3d4e.12345678"
}

json

{
  "Errors": [
    {
      "Code": 8,
      "Message": "Invalid recipient email address"
    }
  ]
}

txt

1: Missing DomainID parameter
2: Sender domain not found (also returned when the domain exists but is owned by another user)
3: Missing To parameter
8: Invalid recipient email address
11: Test message delivery failed (downstream SMTP/PHPMail/etc. rejected the send; HTTP 502)
99: Not available in demo mode (HTTP 403)

Detect DNS Host New in 5.9.x

GET /api/v1/user.senderdomain.dnshost

API Usage Notes

Authentication required: User API Key
Required permissions: User.Update
Rate limit: 100 requests per 60 seconds
Legacy endpoint access via /api.php is also supported
Result is cached in Redis for 1 hour per domain (NS records change rarely)

Performs a server-side NS lookup for the apex of a sender domain and maps the nameservers to a known DNS provider label (Cloudflare, Route 53, GoDaddy, Namecheap, DigitalOcean, Gandi, OVH, Bluehost, HostGator, eNom, Dynadot, Azure DNS, Google Domains, Google Cloud DNS, Hover, DreamHost, Linode). The raw nameserver list is always returned so the UI can fall back to displaying them verbatim when the mapping is unknown.

The endpoint never throws on lookup failure — a resolver error or unmapped nameserver surfaces as DnsHost='unknown' with the (possibly empty) raw nameserver list. The "DNS via X" subtitle is a nice-to-have for the user-facing UI, not a hard requirement, so callers can trust they'll always get an HTTP 200 once ownership is verified.

Request Body Parameters:

Parameter	Type	Required	Description
Command	String	Yes	API command: `user.senderdomain.dnshost`
SessionID	String	No	Session ID obtained from login
APIKey	String	No	API key for authentication
DomainID	Integer	Yes	Sender domain to inspect. Must be owned by the calling user

bash

curl -X GET "https://example.com/api/v1/user.senderdomain.dnshost?APIKey=your-api-key&DomainID=12"

json

{
  "Success": true,
  "DomainID": 12,
  "SenderDomain": "example.com",
  "DnsHost": "Cloudflare",
  "Nameservers": ["ns1.cloudflare.com", "ns2.cloudflare.com"]
}

json

{
  "Success": true,
  "DomainID": 12,
  "SenderDomain": "example.com",
  "DnsHost": "unknown",
  "Nameservers": ["ns1.boutique-host.example.", "ns2.boutique-host.example."]
}

json

{
  "Errors": [
    {
      "Code": 2,
      "Message": "Sender domain not found"
    }
  ]
}

txt

1: Missing DomainID parameter
2: Sender domain not found (also returned when the domain exists but is owned by another user)

User Sender Domain API Documentation ​

List User Sender Domains ​

Get a Sender Domain ​

Create a Sender Domain ​

Update a Sender Domain ​

Delete a Sender Domain ​

Verify a Sender Domain ​

Get DNS Records for a Sender Domain ​

Send a Test Email New in 5.9.x ​

Detect DNS Host New in 5.9.x ​

User Sender Domain API Documentation

List User Sender Domains

Get a Sender Domain

Create a Sender Domain

Update a Sender Domain

Delete a Sender Domain

Verify a Sender Domain

Get DNS Records for a Sender Domain

Send a Test Email New in 5.9.x

Detect DNS Host New in 5.9.x