Rate limits
The API limits how many requests you can make in a short window, as a safety rail against runaway clients. This is separate from token costs: rate limits cap how often you call, while token costs measure how much data you use. Even a free (0-token) call counts toward the rate limit.
The limits
Section titled “The limits”The limit applies per Land Insights account and is shared across all of your keys:
- Up to 120 requests in a burst.
- After that, up to 60 requests per minute sustained.
Skip trace
Section titled “Skip trace”The skip trace endpoints (by name and by property ID) share their own, tighter limit in addition to the general one — each call queries an upstream data provider with limited capacity:
- Up to 10 requests in a burst.
- After that, up to 20 requests per minute sustained.
Skip trace calls can also return a 429 when the upstream provider is
saturated, even if you are under your own limit. This is rare and momentary —
wait the Retry-After interval (one second) and retry.
Going over the limit
Section titled “Going over the limit”If you exceed the limit, the API returns a 429 error with a Retry-After
header telling you how many seconds to wait before trying again. The
X-RateLimit-* headers on every
response let you pace your requests before you hit the limit.