Perform Bulk IP Lookups With Our Batch API Endpoint

To allow a way for customers to perform a single request that returns data for more than one IP, we offer a batch IP API endpoint.

For a bit of backstory behind the development of this feature, one of IPinfo’s valued customers needed to run a lookup on 40 million domains. Without the availability of our batch API endpoint, processing this volume of requests took several hours. Now, that’s been cut to just 10 minutes.

Our batch API endpoint allows you to group up to 1,000 IPinfo API requests into one, regardless of what type of data you need. You POST a list of IPinfo API URLs as a JSON array, a newline separated list, or a space separated list and the response is a JSON object with the URLs as keys and the responses as values.

This endpoint can work together with our many others, such as the ASN, IP ranges, and hosted domains endpoints. This functionality helps businesses and developers to more cleanly and efficiently implement IPinfo’s API into their workflow. The endpoint supports URL patterns, so you can mix and match different IPinfo APIs in a single batch. For example, you can combine standard IP lookups, Lite lookups, and specific field queries (such as country_code or anonymous) in the same request:

lookup/71.181.13.80
lite/157.47.66.225
8.8.4.4/anonymous
AS52188
domains/1.1.1.1
ranges/nytimes.com

curl -XPOST --data '["lite/8.8.4.4", "lite/8.8.4.4/country", "8.8.4.4/anonymous", "1.1.1.1"]' \
"api.ipinfo.io/batch?token=147575b3637788"

Two endpoint variants are available:

• api.ipinfo.io/batch — the default, which uses the full /lookup response and is available on paid plans.
• api.ipinfo.io/batch/lite — dedicated to the Lite API and available to free-tier users as well.

This works alongside our other endpoints, including ASN, IP ranges, hosted domains, and residential proxy detection. An optional filter parameter can also be set to drop URLs that return no data, which is useful for tasks like finding hostnames across a range of IPs.

For request volume tracking, the call to /batch itself is not counted, but each URL inside the batch is. A single call with 100 URLs counts as 100 requests.

To get started, add your API token and POST your list of URLs to the batch endpoint. If you need help integrating batch lookups into your workflow, or if you'd like to suggest a feature, our support team is happy to assist.