REST API · v1

API reference

Verify individual addresses, process batches, discover likely professional emails, and monitor service health through one JSON API.

Production base URL

https://api.mailverifio.com/v1

Authentication

Authorization: Bearer YOUR_API_KEY

Quick start

Replace YOUR_API_KEY with the bearer token configured on your deployment. All bodies and responses use JSON.

GET

Health check

Full reference
cURL · GET /health
curl --request GET \
  --url https://api.mailverifio.com/v1/health \
  --header 'Authorization: Bearer YOUR_API_KEY'
POST

Verify one email

Full reference
cURL · POST /verify
curl --request POST \
  --url https://api.mailverifio.com/v1/verify \
  --header 'Authorization: Bearer YOUR_API_KEY' \
  --header 'Content-Type: application/json' \
  --data '{"email":"person@example.com"}'
POST

Verify a batch

Full reference
cURL · POST /verify/bulk
curl --request POST \
  --url https://api.mailverifio.com/v1/verify/bulk \
  --header 'Authorization: Bearer YOUR_API_KEY' \
  --header 'Content-Type: application/json' \
  --data '{
    "emails": [
      "ada@example.com",
      "grace@example.org",
      "linus@example.net"
    ]
  }'
POST

Find an email

Full reference
cURL · POST /find
curl --request POST \
  --url https://api.mailverifio.com/v1/find \
  --header 'Authorization: Bearer YOUR_API_KEY' \
  --header 'Content-Type: application/json' \
  --data '{
    "firstName": "Ada",
    "lastName": "Lovelace",
    "domain": "example.com"
  }'

Endpoints

Response envelope

Successful and failed requests include a request ID, elapsed duration in milliseconds, and API version. Keep the request ID when investigating an issue.

json
{
  "success": true,
  "data": { "...": "endpoint-specific payload" },
  "meta": {
    "requestId": "req_example",
    "duration": 84,
    "version": "v1"
  }
}

Local development

The production API subdomain rewrites /v1/*. During local development, call http://localhost:3000/api/v1 directly.