Skip to content
MailVet
Updated November 13, 2026

Rate limits

Published, per endpoint, per account. Every response tells you where you stand.

Limits per account

EndpointLimit
GET /v1/verify2,000 requests per second
GET /v1/verify/{id}2,000 requests per second
POST /v1/bulk3 jobs per second
GET /v1/bulk/{id}50 requests per second
GET /v1/bulk/{id}/results10 requests per second
GET /v1/account10 requests per second

Limits are shared by all keys on an account. Need more? Email us with your expected peak.

Headers and 429s

When you go over, the API returns HTTP 429 with Retry-After in seconds. Back off and retry; nothing is charged for a rejected request.

HTTP/1.1 200 OK
X-RateLimit-Limit: 2000
X-RateLimit-Remaining: 1873
X-RateLimit-Reset: 1763026868

HTTP/1.1 429 Too Many Requests
Retry-After: 1
{ "error": { "code": "rate_limited", "message": "2000 requests per second exceeded" } }

What the limit measures

2,000 per second is how many requests the API accepts, not how fast each check completes. Most checks finish in seconds; deeper catch-all checks that need longer come back as pending and finish by webhook, without holding your connection or your rate limit.