Skip to Content

Create identity

Register a new sending identity. Returns the DNS records you need to publish (for DOMAIN) or a verification token (for EMAIL_ADDRESS).

POST /api/v1/partner/email/identities

Request body

{ "identity_type": "DOMAIN", "identity_value": "yourcompany.com" }
FieldTypeRequiredNotes
identity_typestringyesDOMAIN or EMAIL_ADDRESS
identity_valuestringyesThe domain (e.g. yourcompany.com) or full email address

Response

For DOMAIN:

{ "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:dmarc@splashifypro.com"} } }

Publish all three records on your DNS provider, then call /verify to confirm.

For EMAIL_ADDRESS:

{ "success": true, "identity_type": "EMAIL_ADDRESS", "identity_value": "alerts@yourcompany.com", "status": "PENDING", "verification_token": "abc123..." }

We email a confirmation link to the address. Click it (or POST the token via /verify) to mark the identity verified.

cURL

curl https://apis.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"}'

Common errors

StatusCodeMeaning
400INVALID_REQUESTBad domain format / invalid email
400PUBLIC_DOMAIN_BLOCKEDPublic-mail-provider domain (gmail.com, yahoo.com, etc.) — not allowed
400IDENTITY_LIMIT_REACHEDSandbox account hit the 25-identity cap. The cap is lifted automatically once production access is approved — see below.

About the identity cap

Account stateIdentity cap
Sandbox (default for new accounts)25 identities (domains + email addresses combined)
Production access approvedUnlimited

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) and peak-rate cap (1/sec → 14/sec). Submit at POST /partner/email/production-access or via the partner panel’s Production Access tab.

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 support@splashifypro.in with the use case.