POST /v1/validate
Validate a single email address through the 4-layer validation pipeline.Endpoint
Headers
| Header | Required | Description |
|---|---|---|
Content-Type | Yes | Must be application/json |
X-API-Key | Yes | Your API key (gtm_test_* or gtm_live_*) |
Request Body
| Field | Type | Required | Description |
|---|---|---|---|
email | string | Yes | The email address to validate |
Example Request
Response
Success Response (200 OK)
Valid Personal Email
Role-Based Email (FREE)
Catch-All Domain (FREE)
Invalid Email (FREE)
Unknown Verification (FREE)
Response Fields
The validated email address
Validation result:
valid, valid_role_based, risky, invalid, or unknownSee Result Categories for detailsHuman-readable explanation of the validation result
true if the email is a generic business inbox (info@, support@, etc.)true if the domain is a free email provider (Gmail, Yahoo, Outlook, etc.)true if the domain accepts all email addresses (can’t verify specific mailbox)Confidence level:
high, medium, or low (only present if is_catch_all is true)B2B outbound value:
high (worth using), low (role-based), or none (invalid/risky)See B2B Quality Scoring for detailsNumber of credits charged:
0 (free) or 1 (charged)Only valid personal emails with b2b_outbound_quality: "high" are chargedExplanation of why credits were or weren’t charged
Category of role-based email (e.g., “information”, “support”, “sales”)Only present if
is_role_based is trueLayer where validation stopped:
syntax, dns, smtp, or catchallUseful for debugging failuresRaw SMTP server response (when applicable)Useful for understanding SMTP-level issues
Error Responses
400 Bad Request
- Missing
emailfield - Empty email string
- Malformed JSON
401 Unauthorized
- Missing
X-API-Keyheader - Invalid or revoked API key
- Incorrect API key format
429 Too Many Requests
retry_after seconds before making more requests
500 Internal Server Error
Performance
- Cached DNS: ~50ms average
- Uncached DNS: ~500ms average
- Full SMTP validation: ~2s average
Best Practices
Error Handling
Always handle all possible result types:Rate Limiting
For high-volume validation, use the bulk endpoint:Next Steps
Bulk Validation
Validate up to 100 emails at once
Result Categories
Understand all validation results