Snov.io · Rate Limits

Snov Rate Limits

The Snov.io API is rate limited to 60 requests per minute across all endpoints. Separately, most search, finder, verification, and enrichment operations consume credits from the account's monthly plan balance, so throughput is bounded by both the per-minute request cap and the remaining credit quota. Asynchronous endpoints follow a start/result pattern - a POST to /start returns a task_hash and the GET /result (or webhook) delivers the outcome - which also paces effective usage.

Snov Rate Limits is the machine-readable rate-limit profile for Snov.io on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring requests, emails, prospects, and credits.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Sales Engagement, Email Finder, Email Verification, Rate Limiting, and Quotas.

4 Limits Throttle: 429
Sales EngagementEmail FinderEmail VerificationRate LimitingQuotasThrottling

Limits

Requests Per Minute account
requests
60
Applies across all API endpoints for the account.
Emails Per Verification Request request
emails
10
Up to 10 emails may be submitted in a single /v2/email-verification/start call.
Prospects Per Finder Request request
prospects
10
Bulk email finder supports up to 10 prospects per request.
Credit Balance account
credits
see plan
Metered operations draw from the monthly plan credit allotment; free calls (balance, domain email count, sender list) do not consume credits.

Policies

Token Expiry
OAuth2 access tokens expire after 3600 seconds; clients must refresh via /v1/oauth/access_token.
Asynchronous Results
Search and verification use a start/result (task_hash) pattern; poll the /result endpoint or register a webhook_url instead of tight looping.
Backoff Strategy
On HTTP 429, back off and retry within the 60 requests-per-minute budget; honor Retry-After when present.

Sources