Verify Sending Domain

POST

api

websites

{domain}

verify

Verify Sending Domain

curl --request POST \
  --url https://api.sequenzy.com/api/v1/websites/{domain}/verify \
  --header 'Authorization: Bearer <token>'

const options = {method: 'POST', headers: {Authorization: 'Bearer <token>'}};

fetch('https://api.sequenzy.com/api/v1/websites/{domain}/verify', options)
  .then(res => res.json())
  .then(res => console.log(res))
  .catch(err => console.error(err));

<?php

$curl = curl_init();

curl_setopt_array($curl, [
  CURLOPT_URL => "https://api.sequenzy.com/api/v1/websites/{domain}/verify",
  CURLOPT_RETURNTRANSFER => true,
  CURLOPT_ENCODING => "",
  CURLOPT_MAXREDIRS => 10,
  CURLOPT_TIMEOUT => 30,
  CURLOPT_HTTP_VERSION => CURL_HTTP_VERSION_1_1,
  CURLOPT_CUSTOMREQUEST => "POST",
  CURLOPT_HTTPHEADER => [
    "Authorization: Bearer <token>"
  ],
]);

$response = curl_exec($curl);
$err = curl_error($curl);

curl_close($curl);

if ($err) {
  echo "cURL Error #:" . $err;
} else {
  echo $response;
}

package main

import (
	"fmt"
	"net/http"
	"io"
)

func main() {

	url := "https://api.sequenzy.com/api/v1/websites/{domain}/verify"

	req, _ := http.NewRequest("POST", url, nil)

	req.Header.Add("Authorization", "Bearer <token>")

	res, _ := http.DefaultClient.Do(req)

	defer res.Body.Close()
	body, _ := io.ReadAll(res.Body)

	fmt.Println(string(body))

}

require 'uri'
require 'net/http'

url = URI("https://api.sequenzy.com/api/v1/websites/{domain}/verify")

http = Net::HTTP.new(url.host, url.port)
http.use_ssl = true

request = Net::HTTP::Post.new(url)
request["Authorization"] = 'Bearer <token>'

response = http.request(request)
puts response.read_body

{
  "success": true,
  "verified": true,
  "readyToSend": false,
  "message": "Domain DNS records verified. Sending is not available yet: this domain is still being activated for sending. No further DNS changes are needed - sending unlocks automatically once activation finishes.",
  "discarded": false,
  "website": {
    "id": "domain_abc123",
    "domain": "mail.example.com",
    "status": "verified",
    "dnsVerified": true,
    "readyToSend": false,
    "readiness": {
      "status": "activating",
      "reason": "activation_pending"
    },
    "dkim": { "type": "byodkim", "status": "verified", "diagnostic": null },
    "spf": { "status": "verified", "record": {}, "diagnostic": null },
    "mailFrom": { "status": "verified", "domain": "send.mail.example.com", "mxRecord": {}, "diagnostic": null },
    "appleEmailSources": ["send.mail.example.com", "example.com"],
    "tracking": { "policy": "legacy", "required": false, "hostname": "links.example.com", "status": "verified", "ready": true, "error": null, "cnameRecord": { "type": "CNAME", "name": "links.example.com", "value": "links1.sequenzydns.com" } }
  }
}

{
  "success": false,
  "code": "SENDING_DOMAIN_NOT_CONFIGURED",
  "error": "Sending domain not configured",
  "title": "Sending domain not configured",
  "description": "The domain \"mail.example.com\" has not been added as a sending domain for this company, so it cannot be checked or verified yet.",
  "resolution": "Call add_sending_domain with domain \"mail.example.com\" first, publish the DNS records it returns (DKIM, the bounce records described by website.bounceRecords, and DMARC when present), then call verify_sending_domain after DNS changes propagate.",
  "docsUrl": "https://docs.sequenzy.com/api-reference/websites/create",
  "details": {
    "domain": "mail.example.com"
  }
}

Run the sending-domain DNS verification pipeline immediately and return DNS status separately from sending readiness. verified is the fresh DNS verdict. The company tracking domain is never part of it; this check also rechecks the tracking domain without letting it affect the domain. readyToSend additionally requires the domain to finish activating for sending. message reports both: when DNS is verified but activation is still running, it says so instead of claiming the domain can send. This endpoint uses the same verification process as the dashboard and updates the stored status.

Custom reply DNS recovery

Reply routing is separate from sending readiness. Once a legacy reply domain’s MX verifies, this endpoint prepares any additional ownership TXT record in website.dnsRecords.inboundVerificationRecord (name and value). The value is a public DNS token, not an API credential. Publish it at the returned fully qualified name and call this endpoint again after DNS propagation. A pending verification returns HTTP 200 with inboundRoutingStatus: "failed" and a retry instruction in inboundRoutingError; it does not make a verified sending domain unable to send. inboundVerificationStatus reports ownership only. Use inboundRoutingStatus: "active" to confirm the stored routing checks passed. Missing MX leaves routing pending. Provider lookup/preparation errors can be retried with this same endpoint. An inconclusive ownership lookup preserves an existing active route and records an error rather than discarding accepted replies. Previously confirmed ownership remains verified; an unchecked legacy SES route still displays pending until its first successful ownership check. discarded: true means a concurrent update superseded this check; read the current website or retry before acting on stale results. Repeated checks reuse a pending token. Expired verification is restarted and the current returned token is authoritative. Already-sent reply addresses and their MX remain unchanged. A required TXT stays available after verification; an unnecessary pending TXT instruction disappears when a parent verifies. These generated fields are read-only: no request parameter sets, clears, or replaces them. A missing record alone does not prove routing is ready; its preparation may not have run or may have failed. CLI: sequenzy websites verify mail.example.com --company comp_123. MCP: verify_sending_domain. Both return the same records and retry status.

Request

string

required

Configured sending domain.

curl -X POST "https://api.sequenzy.com/api/v1/websites/mail.example.com/verify" \
  -H "Authorization: Bearer YOUR_API_KEY"

Responses

{
  "success": true,
  "verified": true,
  "readyToSend": false,
  "message": "Domain DNS records verified. Sending is not available yet: this domain is still being activated for sending. No further DNS changes are needed - sending unlocks automatically once activation finishes.",
  "discarded": false,
  "website": {
    "id": "domain_abc123",
    "domain": "mail.example.com",
    "status": "verified",
    "dnsVerified": true,
    "readyToSend": false,
    "readiness": {
      "status": "activating",
      "reason": "activation_pending"
    },
    "dkim": { "type": "byodkim", "status": "verified", "diagnostic": null },
    "spf": { "status": "verified", "record": {}, "diagnostic": null },
    "mailFrom": { "status": "verified", "domain": "send.mail.example.com", "mxRecord": {}, "diagnostic": null },
    "appleEmailSources": ["send.mail.example.com", "example.com"],
    "tracking": { "policy": "legacy", "required": false, "hostname": "links.example.com", "status": "verified", "ready": true, "error": null, "cnameRecord": { "type": "CNAME", "name": "links.example.com", "value": "links1.sequenzydns.com" } }
  }
}

{
  "success": false,
  "code": "SENDING_DOMAIN_NOT_CONFIGURED",
  "error": "Sending domain not configured",
  "title": "Sending domain not configured",
  "description": "The domain \"mail.example.com\" has not been added as a sending domain for this company, so it cannot be checked or verified yet.",
  "resolution": "Call add_sending_domain with domain \"mail.example.com\" first, publish the DNS records it returns (DKIM, the bounce records described by website.bounceRecords, and DMARC when present), then call verify_sending_domain after DNS changes propagate.",
  "docsUrl": "https://docs.sequenzy.com/api-reference/websites/create",
  "details": {
    "domain": "mail.example.com"
  }
}

Verify Sending Domain

curl --request POST \
  --url https://api.sequenzy.com/api/v1/websites/{domain}/verify \
  --header 'Authorization: Bearer <token>'

const options = {method: 'POST', headers: {Authorization: 'Bearer <token>'}};

fetch('https://api.sequenzy.com/api/v1/websites/{domain}/verify', options)
  .then(res => res.json())
  .then(res => console.log(res))
  .catch(err => console.error(err));

<?php

$curl = curl_init();

curl_setopt_array($curl, [
  CURLOPT_URL => "https://api.sequenzy.com/api/v1/websites/{domain}/verify",
  CURLOPT_RETURNTRANSFER => true,
  CURLOPT_ENCODING => "",
  CURLOPT_MAXREDIRS => 10,
  CURLOPT_TIMEOUT => 30,
  CURLOPT_HTTP_VERSION => CURL_HTTP_VERSION_1_1,
  CURLOPT_CUSTOMREQUEST => "POST",
  CURLOPT_HTTPHEADER => [
    "Authorization: Bearer <token>"
  ],
]);

$response = curl_exec($curl);
$err = curl_error($curl);

curl_close($curl);

if ($err) {
  echo "cURL Error #:" . $err;
} else {
  echo $response;
}

package main

import (
	"fmt"
	"net/http"
	"io"
)

func main() {

	url := "https://api.sequenzy.com/api/v1/websites/{domain}/verify"

	req, _ := http.NewRequest("POST", url, nil)

	req.Header.Add("Authorization", "Bearer <token>")

	res, _ := http.DefaultClient.Do(req)

	defer res.Body.Close()
	body, _ := io.ReadAll(res.Body)

	fmt.Println(string(body))

}

require 'uri'
require 'net/http'

url = URI("https://api.sequenzy.com/api/v1/websites/{domain}/verify")

http = Net::HTTP.new(url.host, url.port)
http.use_ssl = true

request = Net::HTTP::Post.new(url)
request["Authorization"] = 'Bearer <token>'

response = http.request(request)
puts response.read_body

{
  "success": true,
  "verified": true,
  "readyToSend": false,
  "message": "Domain DNS records verified. Sending is not available yet: this domain is still being activated for sending. No further DNS changes are needed - sending unlocks automatically once activation finishes.",
  "discarded": false,
  "website": {
    "id": "domain_abc123",
    "domain": "mail.example.com",
    "status": "verified",
    "dnsVerified": true,
    "readyToSend": false,
    "readiness": {
      "status": "activating",
      "reason": "activation_pending"
    },
    "dkim": { "type": "byodkim", "status": "verified", "diagnostic": null },
    "spf": { "status": "verified", "record": {}, "diagnostic": null },
    "mailFrom": { "status": "verified", "domain": "send.mail.example.com", "mxRecord": {}, "diagnostic": null },
    "appleEmailSources": ["send.mail.example.com", "example.com"],
    "tracking": { "policy": "legacy", "required": false, "hostname": "links.example.com", "status": "verified", "ready": true, "error": null, "cnameRecord": { "type": "CNAME", "name": "links.example.com", "value": "links1.sequenzydns.com" } }
  }
}

{
  "success": false,
  "code": "SENDING_DOMAIN_NOT_CONFIGURED",
  "error": "Sending domain not configured",
  "title": "Sending domain not configured",
  "description": "The domain \"mail.example.com\" has not been added as a sending domain for this company, so it cannot be checked or verified yet.",
  "resolution": "Call add_sending_domain with domain \"mail.example.com\" first, publish the DNS records it returns (DKIM, the bounce records described by website.bounceRecords, and DMARC when present), then call verify_sending_domain after DNS changes propagate.",
  "docsUrl": "https://docs.sequenzy.com/api-reference/websites/create",
  "details": {
    "domain": "mail.example.com"
  }
}

​Custom reply DNS recovery

​Request

​Responses

Custom reply DNS recovery

Request

Responses