Rate Limit & Quotas
You can use a certain number of requests per month, defined by your plan.
Once you go over this quota, the API returns a 429 HTTP status code, and you either need to upgrade your plan or wait until the end of the month. We enforce a minute rate limit for specific plans. If you exceed this, the API returns a 429 HTTP status code. You then have to wait until the end of the minute to make more requests. Not every request counts towards your monthly request volume.
Not every request counts
Only successful calls count against your quota. Any error on our side or validation errors (e.g., wrong parameter) will NOT count against your quota or rate limit.
Example request
curl "https://api.ipbase.com/v2/info?ip=1.1.1.1&apikey=YOUR-APIKEY"
Response Headers
Every metered response carries headers that tell you your monthly quota and how many requests you have remaining in the current period:
X-RateLimit-Limit-Quota-Month: 300
X-RateLimit-Remaining-Quota-Month: 199
On plans with a per-minute rate limit, matching -Minute variants of these headers are included as well.
Each response also includes an X-Cost header stating how many requests the call counted against your quota — 1 for a normal billed request, 0 for requests that are free of charge (e.g. requests made with a sandbox API key):
X-Cost: 1
If you are currently consuming a grace quota (e.g. while a payment is being completed), the monthly headers are replaced by their -Grace- variants:
X-RateLimit-Limit-Grace-Month: 100
X-RateLimit-Remaining-Grace-Month: 42
If overages are enabled for your plan and you exceed your monthly quota, the overage headers are sent in addition to the (exhausted) monthly headers:
X-RateLimit-Limit-Overage-Month: 500
X-RateLimit-Remaining-Overage-Month: 350
You can also check your current quota usage at any time — without spending a request — via the status endpoint.