Rate Limits
Quota and throttling behavior for the VPNDetection HTTP API.
On this page
On Unlimited, the free plan, lookups have no daily or monthly cap, with a key or without one. A burst can still get a 429 with Retry-After, below. POST /batch needs a paid plan: a batch of more than one address answers 401 with no key and 402 with a key on the free plan.
On a paid plan, its monthly quota is the limit that matters. We don't publish a per-second limit, so send what your integration needs. A burst can still get a 429 with Retry-After, below.
- You may use the Database Download API for any dataset you license as much as you like.
- All other endpoints have very high and undocumented rate limits.
Past your quota
Overage is off until you turn it on in Billing. Until then, once a paid plan's monthly quota is used, its lookups still answer 200 with Unlimited's fields and cap_reached: true until the month rolls over, and aren't charged. To keep every field past the quota, set an overage cap in Billing: lookups past the quota are then billed as overage up to the cap, or with no limit if you leave the cap empty, and past the cap they answer as Unlimited's again. Every answer to a paid key carries cap_reached, false until then.
An answer with Unlimited's fields counts toward Unlimited's per-minute limit for your account, past which a 429 carries Retry-After.
Reading a 429
Every 429 is a rate limit, with a key or without one: wait the seconds Retry-After gives and the request will go through. The official client libraries already retry it.