Endpoint
Authentication
| Header | Required | Value |
|---|---|---|
X-API-Key | Yes | Your API key (bun_...) |
Content-Type | Yes | application/json |
Overview
Validate an email address across multiple layers: syntax format, DNS MX record existence, and role-based address detection. The response also includes a typo suggestion for common domain misspellings, allowing you to prompt users to correct obvious mistakes before they submit.Use cases
- Block invalid addresses at signup to reduce bounce rates
- Scrub lead lists and newsletter databases before campaign sends
- Enforce deliverable email requirements in CRM intake forms
- Surface correction suggestions to users who mistype common domains
Request body
| Field | Type | Required | Description |
|---|---|---|---|
email | string | Yes | The email address to validate |
Example
Response
200 OK
| Field | Type | Description |
|---|---|---|
email | string | The email address that was evaluated |
valid | boolean | true when both format and MX checks pass |
checks | object | Individual check results: format (boolean), mx (boolean), role (boolean — true if role-based) |
mx_records | array | List of MX records, each with priority (integer) and exchange (string) |
suggestion | string | Corrected email if a common typo was detected, otherwise null |

