Skip to content
Splashify Pro
Email docsEmail

Verify identity

Re-run DNS verification for a domain identity (after publishing records), or send a new confirmation link for an email-address identity.

POST

/api/v1/partner/email/identities/:type/:value/verify

Domain verification

bash
curl -X POST \
  https://api.splashifypro.com/api/v1/partner/email/identities/DOMAIN/yourcompany.com/verify \
  -H "Authorization: Bearer $SPLASHIFY_API_KEY"

Response:

json
{
  "success": true,
  "status": "VERIFIED",
  "spf_ok": true,
  "dkim_ok": true,
  "dmarc_ok": true,
  "dns_records": { ... }
}

When all three records pass, status flips to VERIFIED. If any record fails, status is PENDING, also for a domain that was VERIFIED before. The per-record pass flags tell you which records to fix.

If a DNS lookup fails on our side, the call returns 503 Service Unavailable and your identity stays as it was. Try again in a minute.

Domain already verified on another account

SPF, DKIM and DMARC are the same for every customer, so they cannot show which account controls a domain. If the domain is already verified on another account, in Splashify Pro Email or in the Splashify Pro app, you also add one TXT record that belongs to your account. It shows up in dns_records with the other records, under ownership, with a purpose that says why it is there:

json
{
  "success": true,
  "status": "PENDING",
  "spf_ok": true,
  "dkim_ok": true,
  "dmarc_ok": true,
  "ownership_ok": false,
  "dns_records": {
    "spf": { "...": "..." },
    "dkim": { "...": "..." },
    "dmarc": { "...": "..." },
    "ownership": {
      "type": "TXT",
      "hostname": "_splashify-verify.yourcompany.com",
      "value": "splashify-verify=4f0c9e1ab27d46c88e13f5b07a6d2c19",
      "pass": false,
      "purpose": "This domain is already verified on another account. Add this TXT record to show that you control the domain too. Keep it in place."
    }
  }
}

Publish it, keep your other records, and call this endpoint again. The status flips to VERIFIED once all the records pass, including this one.

  • The value is different for each account and each domain, so copy it from your own response. One zone can hold a value for each account that sends from the domain.
  • You do not need this record if nobody else has verified the domain, or if your own identity is already VERIFIED. The list never shows it then.
  • Nothing changes for the account that verified the domain first.

Keep the record in place. If your identity ever goes back to PENDING while another account holds the domain, it is needed again.

If we cannot finish this check on our side, the call returns 503 Service Unavailable and your identity stays as it was. Try again in a minute.

Email-address verification

An address is verified only when someone opens the link we email to it and presses the button on that page, so no API call can verify one. This call sends a new link, for example when the first has expired. The new link replaces the old one.

bash
curl -X POST \
  https://api.splashifypro.com/api/v1/partner/email/identities/EMAIL_ADDRESS/[email protected]/verify \
  -H "Authorization: Bearer $SPLASHIFY_API_KEY"

Response:

json
{
  "success": true,
  "status": "PENDING",
  "confirmation_sent": true
}

confirmation_sent is false if the email could not go out: call again in a minute. For an address already confirmed nothing is sent, and the response is { "success": true, "status": "VERIFIED" }.

The link works once and expires after 24 hours. It opens a page with a Confirm this address button, and nothing changes until the button is pressed, so a mail scanner that follows the link confirms nothing. Once it is pressed, the address can send right away, in sandbox too. Opening the link again after that does no harm. An expired or replaced link opens a page that says so and changes nothing.

Rate limiting

A confirmation email goes to an address you choose, so it has limits, which also apply when you add an address:

When we check

We check a domain when you add it and each time you call this endpoint. SPF, DKIM and DMARC are not checked in the background, so call this endpoint after you change your DNS. A bounce domain is: we re-check a pending one during its first week and a verified one once a day.

Common errors