Getting Started with VeriMail API
Real-time email validation for clean data
Start VerifyingCreate Your VeriMail Account
Jumpstart your integration by registering a developer account. You’ll receive instant access to the dashboard and 1,000 free monthly verification credits.
Register via Dashboard
Navigate to app.verimail.io/register, enter your work email, and verify your domain. Account activation takes under 60 seconds.
Configure Workspace
Set your organization name, select your base region (US-EAST or EU-WEST), and enable two-factor authentication for secure API access.
Once registered, you’ll be redirected to the Developer Console where your project sandbox is pre-configured.
Generate Your API Key
Secure your connection by creating a production-ready API key. VeriMail uses HMAC-SHA256 signing for all authenticated endpoints.
Navigate to Credentials
In the left sidebar, click Settings > API Keys. Toggle the switch for “Production Environment” to reveal the key generator.
Scope & Save
Assign the “verify:read” and “verify:write” scopes. Copy the generated `vm_live_` prefixed token immediately, as it will not be displayed again.
Store your key in environment variables or a secrets manager. Never hardcode credentials in client-side JavaScript or public repositories.
Make Your First Verification Request
Send a POST request to our validation endpoint to test a single email address. The API returns results in under 200 milliseconds.
Endpoint & Headers
Target `https://api.verimail.io/v1/verify`. Include `Authorization: Bearer vm_live_your_key` and set `Content-Type: application/json`.
Payload Structure
Pass a JSON body with the `email` field. Optional parameters include `check_disposable`, `check_role_account`, and `strict_mode` for compliance tuning.
Run the request through your preferred HTTP client. A successful call returns a 200 OK status with the validation payload.
Parse the Response Format
VeriMail returns a structured JSON object containing deliverability scores, syntax checks, and SMTP handshake results.
Core Validation Fields
The `status` field outputs `valid`, `invalid`, `risky`, or `unknown`. The `score` provides a 0–100 confidence metric based on mailbox existence and domain reputation.
Diagnostic Metadata
Review `mx_records`, `catch_all`, `disposable`, and `free_provider` booleans to filter lists according to your CRM’s compliance rules.
Error Handling
Rate limits return HTTP 429 with a `Retry-After` header. Authentication failures trigger HTTP 401 with a clear message to rotate your credentials.
Map these fields to your database schema to maintain clean lists and reduce bounce rates below 0.5%.
View Full Schema Documentation Download SDKs