Overview of IPinfo API endpoints

General
1

In 2025, we began investing in new products (Lite, Core, and Plus) and building a new API system from scratch to support the Trillions of API requests we receive every month and incorporate feedback from IPinfo users and the community.

We still retain full operation, maintenance, and frequent updates to our now “legacy” API system. We are not asking our existing users to migrate, but if they want to do so, they can.

IPinfo API Services (3)
IPinfo API Services (3)2240×1260 155 KB

Legacy API system

ipinfo.io

When it comes to the IP address connection from which the user is making a request, we supported two endpoints:

  • ipinfo.io: Our default API endpoint. This API endpoint was not dual-stacked and supported queries only from IPv4 connections. IPinfo API’s IPv6 endpoint: v6.ipinfo.io.
  • v6.ipinfo.io: To support users and devices on an IPv6 connection.

By making an API call to the endpoint, we provided the data to which you had access based on your subscription tier. There is no need to add any specific API subURL.

The API endpoint:

  • Supports token and tokenless requests
  • Provides the user with only the IP information they have access to
  • Returns the device’s IP information if an IP address parameter is not provided

Please note that this API system is still functional, and we have not changed anything in it.

Updated API system

api.ipinfo.io

In 2025, through the release of the bundles API product, we engineered a new API system from scratch.

We now have 3 API subdomains for handling requests from IP addresses connections (IPv4 or IPv6) to our API.

  • api.ipinfo.io: The default dual-stacked API system. Because the API system is dual-stacked, you can access the API from both IPv4 and/or IPv6 connections. If your server is on a dual-stack connection and you want information on your IP address, our API will prefer your IPv6 connection over IPv4.
  • v4.api.ipinfo.io: A dedicated API system to support IPv4 connection.
  • v6.api.ipinfo.io: A dedicated API system to support IPv6 connection.

Now, if you need information on both your IPv6 and IPv4 connections, we recommend making asynchronous requests to both of these endpoints simultaneously.

Now, besides the connection-level access, there are some API structural changes.

  • /ip: This API endpoint returns your public IP address. Note that this API endpoint supports unlimited requests without an access token. You can access this API endpoint in the following ways:
    • api.ipinfo.io/ip: Default endpoint to return your public IP address. If you are on a dual stack connection, it will return your IPv6 IP address.
    • v4.api.ipinfo.io/ip: Returns your IPv4 public IP address if you are using it.
    • v6.api.ipinfo.io/ip: Returns your IPv6 public IP address if you are using it.
  • /lite: The IPinfo lite API service is available to all users, even those in the paid tier.
  • /lookup: If you are on a paid tier, you need to use the /lookup endpoint.
  • To get your or requesting devices’s IP information, use the /me API sub-URL to the API query. api.ipinfo.io/lite/me or api.ipinfo.io/lookup/me
2

Just a small observation that the diagram should probably have the v6.api.ipinfo.io in the box for IPv6 API.

3

Nice catch! Thank you very much, Cybersteve! I appreciate it!