Introduction

Every call returns a conservative verdict (valid, invalid, disposable, risky or unknown) plus the individual checks behind it, so you can apply your own policy. The API lets you:

• verify a single address in real time, for example on a signup form;
• submit a list of up to 50,000 addresses and page through the results;
• find the likely address pattern for a person at a company;
• read your plan, credits and usage.

1. A veridock.io account: sign up for 250 free checks a month.
2. An API key from Settings › API keys. Keep private keys server-side.
3. Any HTTP client: cURL, Postman, or your language of choice.

1. Authenticate. Send your key in the Authorization header as a bearer token (or in x-api-key).

2. Verify one address.

curl https://new-project-rho-ecru.vercel.app/v1/verify \
  -H "Authorization: Bearer vd_live_…" \
  -H "Content-Type: application/json" \
  -d '{"email":"person@example.com"}'

3. Verify a list. Credits are reserved up front and the job runs in the background; poll it for results.

curl https://new-project-rho-ecru.vercel.app/v1/bulk/verify \
  -H "Authorization: Bearer vd_live_…" \
  -H "Content-Type: application/json" \
  -d '{"name":"October signups","emails":["a@example.com","b@example.com"]}'

• Authentication: private vs public keys, trusted IPs, allowed origins.
• Response & statuses: what each field means and the recommended policy.
• Errors & rate limits: codes to handle and per-plan limits.

• Treat unknown as "not sure", never as invalid; accept it with a confirmation email.
• Send an Idempotency-Key so retries never double-charge you.
• Respect 429 responses and wait retry_after_ms before retrying.
• Use a public key for browser calls; never ship a private key in client code.

Stuck? Open a ticket from Support in the dashboard and we will answer in the same thread. Happy validating!