Surfe · Rate Limits

Surfe Rate Limits

The Surfe API enforces a per-account request rate limit of up to 10 requests per second, allowing short bursts of up to 20 requests, plus a daily request quota (documented at 2,000 requests/day) that resets at midnight in the user's timezone. Separate from request throttling, enrichment and search consume credits from distinct email, mobile, and search/ICP pools; exhausting a credit pool returns HTTP 402 rather than a throttling response.

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

It captures 4 rate-limit definitions, measuring requests and records.

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

Tagged areas include B2B Data, Contact Data, Enrichment, Rate Limiting, and Quotas.

4 Limits Throttle: 429
B2B DataContact DataEnrichmentRate LimitingQuotasThrottling

Limits

Requests Per Second account
requests
10
Sustained rate limit across the account's API key.
Burst account
requests
20
Short bursts up to 20 requests are tolerated above the 10 rps sustained rate.
Requests Per Day account
requests
2000
Daily request quota; resets at midnight in the user's timezone. Verify on reconciliation.
Bulk Enrichment Batch Size request
records
10000
Maximum people per POST /people/enrich request; processed asynchronously.

Policies

Credit Pools
Email, mobile, and search/ICP credits are metered in separate pools; running out returns HTTP 402 independent of request throttling.
Backoff Strategy
Clients should implement exponential backoff with jitter on 429 responses and honor any Retry-After header.
Async Consumption
Prefer webhooks (notificationOptions.webhookUrl) over polling for bulk enrichment jobs to avoid burning request quota on status checks.

Sources