Skip to content

Rate limit

A rate limit caps how many requests a client may make in a period, which protects the service and keeps usage predictable.

Providers set limits per key, per account or per endpoint. The 1lookup.dev default is 50 requests per second per key, and higher limits are available on request. Limits are about request pace, and they are separate from your credit balance.

Clients should expect to hit a limit during bursts and handle it gracefully. The usual approach is to slow down and retry with exponential backoff and a little random jitter, so many workers do not all retry at the same moment. A queue with a fixed number of concurrent workers keeps a pipeline under the cap.

For large lists, a bulk job is a better fit than a loop of single calls. A bulk submission hands the pacing to the service and reports row-level results when it completes.

[ Validate ][ Enrich ]
[Get started]

Run your first lookup in two minutes

Create a key, pick a plan and call any product in the catalog. Plans start at $29 a month.

[ Screen ][ Scrape ]