Skip to content
Splashify Pro
Email docsEmail

Create identity

Register a new sending identity. Returns the DNS records you need to publish (for DOMAIN), or emails a confirmation link to the address (for EMAIL_ADDRESS).

POST

/api/v1/partner/email/identities

Request body

json
{
  "identity_type": "DOMAIN",
  "identity_value": "yourcompany.com"
}

Response

For DOMAIN:

json
{
  "success": true,
  "identity_type": "DOMAIN",
  "identity_value": "yourcompany.com",
  "status": "PENDING",
  "dns_records": {
    "spf":   {"type": "TXT", "hostname": "yourcompany.com",                  "value": "v=spf1 include:_spf.mail.splashifypro.com ~all"},
    "dkim":  {"type": "CNAME", "hostname": "splashify._domainkey.yourcompany.com", "value": "splashify._domainkey.mail.splashifypro.com"},
    "dmarc": {"type": "TXT", "hostname": "_dmarc.yourcompany.com",           "value": "v=DMARC1; p=quarantine; rua=mailto:[email protected]"}
  }
}

Publish every record in dns_records on your DNS provider (SPF, DKIM and DMARC, plus dkim2 and return_path when present), then call /verify to confirm.

If the domain is already verified on another account, dns_records also lists an ownership TXT record, and the response carries ownership_ok: false. See Domain already verified on another account.

For EMAIL_ADDRESS:

json
{
  "success": true,
  "identity_type": "EMAIL_ADDRESS",
  "identity_value": "[email protected]",
  "status": "PENDING",
  "confirmation_sent": true
}

We email a confirmation link to the address. Someone who can read that mailbox opens it and presses the button on the page, and the identity becomes VERIFIED. The link works once and expires after 24 hours. It never appears in an API response, so holding your API key is not enough to verify an address.

confirmation_sent is false if the email could not go out. The identity is still created: call /verify to send a new link.

Adding an identity that already exists answers 200 with the existing row, and sends no email.

Mail from an address identity is signed with our shared domain, so it fails DMARC for your domain. Read what that means for delivery before you rely on one.

cURL

bash
curl https://api.splashifypro.com/api/v1/partner/email/identities \
  -H "Authorization: Bearer $SPLASHIFY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"identity_type": "DOMAIN", "identity_value": "yourcompany.com"}'

Adding an identity twice

A POST for an identity you already have changes nothing and answers 200 with the existing row, in the same shape as above.

Common errors

About the identity cap

Most accounts only need 1 – 5 identities even at full scale. Verifying a single domain (e.g. mail.yourcompany.com) authorizes every <anything>@mail.yourcompany.com to send, so you rarely need to register individual email addresses separately.

Lifting the cap

The cleanest path is production access — admin reviews your use case once, approves, and the identity cap is removed automatically along with the daily-send cap (200/day → 50,000/day). Submit at POST /partner/email/production-access or via the Production Access tab in Splashify Pro Email.

Working around the cap before production access

If you're still in sandbox and genuinely need to register a new identity but already have 25:

  1. List what's registered — GET /partner/email/identities.
  2. Delete one you no longer send from — DELETE /partner/email/identities/{type}/{value}.
  3. The slot frees immediately; re-try the create call.

If your sandbox use case legitimately needs more than 25 identities (rare — usually means you're adding one EMAIL_ADDRESS per customer where verifying the parent domain would do), email [email protected] with the use case.