Skip to main content

​
Endpoint

POST /v1/deliverability
Cost: 3 credits per request This is a deeper version of the standard email validation. Where /v1/email confirms basic reachability, /v1/deliverability runs an extended SMTP handshake, cross-references known spam trap databases, and applies additional disposable provider detection.

​
Request body

{
  "email": "hello@datalinkapis.com"
}
FieldTypeRequiredDescription
emailstringYesThe email address to check

​
Example request

curl -X POST https://api.datalinkapis.com/v1/deliverability \
  -H "Authorization: Bearer dl_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "email": "hello@datalinkapis.com" }'

​
Response

{
  "email": "hello@datalinkapis.com",
  "deliverable": true,
  "confidence": "high",
  "syntax_valid": true,
  "mx_found": true,
  "smtp_valid": true,
  "spam_trap": false,
  "disposable": false,
  "catch_all": false,
  "role_account": false,
  "free_provider": false,
  "domain": "datalinkapis.com",
  "credits_used": 3
}

​
Response fields

FieldTypeDescription
emailstringThe address that was checked
deliverablebooleanWhether the address is likely to accept mail
confidencestringConfidence level: high, medium, or low
syntax_validbooleanRFC 5321 syntax check
mx_foundbooleanWhether a valid MX record exists
smtp_validbooleanWhether the extended SMTP handshake succeeded
spam_trapbooleanWhether the address matches a known spam trap
disposablebooleanWhether the domain is a disposable provider
catch_allbooleanWhether the domain accepts all addresses regardless of existence
role_accountbooleanWhether this is a role address (info@, support@, etc.)
free_providerbooleanWhether this is a free consumer email provider
domainstringDomain portion of the address
credits_usedintegerCredits deducted — always 3 for this endpoint

​
When to use vs /v1/email

/v1/email (1cr)/v1/deliverability (3cr)
Syntax check✓✓
MX lookup✓✓
SMTP checkBasicExtended handshake
Spam trap detection—✓
Catch-all detection—✓
Confidence score—✓
Use /v1/deliverability when sending to a list where a bounce or spam trap hit would have significant consequences — e.g. cold outreach or transactional flows with strict deliverability SLAs.