Access the Web Like a Local Without Managing Proxies

You don’t shop the same in Austin as you do in Brooklyn. So why should your data pipelines?

Many websites personalize their content based on location — not just by country, but by state and city. That’s why Nimble’s Web API supports hyper-local request targeting. It’s a feature we’ve had running quietly under the hood, and this week we’re bringing it front and center.

You can now send API requests that appear to originate from specific cities and states, giving you access to region-specific content without having to configure proxy infrastructure yourself.

Why We Built It

The modern web is hyper-localized, with businesses personalizing everything about the user experience in real time. Location is one of the key parameters influencing data and user experiences in the online space.

To demonstrate this, we requested information from Amazon on Apple Airpods Pro 2nd Generation through New York City, and parsed out the following pricing information:

...
"oldPrice": "$239.00",
"parent_asin": "B0F8RHPN49",
"price": "$134.42",
"rating": "4.3 out of 5 stars",
"reviewsCount": "1,072 ratings",
...

The same request made from just across the border in Toronto, Canada, returned vastly different pricing information:

...
"oldPrice": "$169.99",
"parent_asin": "B0F8RHPN49",
"price": "$151.96",
"rating": "4.3 out of 5 stars",
"reviewsCount": "1,072 ratings",
...

With the infrastructure for country, state, and city level geotargeting already existing in our Nimble IP proxy service, we made the decision to expand support into our Web API to enable customers to easily implement advanced geotargeting with zero additional setup.

How to Use It

To make a request that reflects a specific geographic origin, simply include country, state, and city:

import requests, base64

auth = base64.b64encode(b"user@example.com:your_password").decode()

res = requests.post(
    "https://api.webit.live/api/v1/realtime/web",
    headers={
        "Authorization": f"Basic {auth}",
        "Content-Type": "application/json"
    },
    json={
        "url": "https://ipinfo.io/json",
        "country": "US",
        "state": "NY",
        "city": "brooklyn",
        "render": "true"
    }
)

print(res.json())

Use our location directory to find valid city/state combinations.

Real-World Example: Google Flights from NYC vs. SF

Let’s say you want to compare Google Flights availability and pricing from different cities.

Even when searching the same route, flight data can shift depending on where the request comes from. This affects:

• Default airports shown
• Regional airline availability
• Localized pricing and currency
• Geo-specific promotions or partners

With Nimble Web API, you can access both perspectives with just a parameter change:

Request from New York, NY

{
  "url": "https://www.google.com/flights",
  "country": "US",
  "state": "NY",
  "city": "new york",
  "render": true
}

Request from San Francisco, CA

{
  "url": "https://www.google.com/flights",
  "country": "US",
  "state": "CA",
  "city": "san francisco",
  "render": true
}

The responses will reflect what an actual user in each location would see — from different airports to different pricing tiers.

This same pattern applies across eCommerce, job boards, maps, local news, and real estate.

When to Use It

This feature is especially valuable for:

• Local SEO tracking - Access regional SERPs, map pack data, and geo-fenced results
• Retail & pricing intelligence - Compare inventory and pricing across store locations
• Market-specific extraction - Get content tailored to the region you're targeting
• Experience testing - Understand how content, offers, or layout vary by location

Best Practices

• Use both state and city fields together for maximum accuracy
• Reference the supported cities list to avoid invalid requests
• Fully compatible with parse, render_flow, merge_dynamic, and batch modes
• Works great with geo-sensitive platforms like Google, Craigslist, Yelp, Amazon, and Booking.com

Go Local - Without the Overhead

Whether you're working on SEO visibility, product localization, or regional intelligence, this feature helps you access location-specific content the right way—cleanly, reliably, and at scale.

No proxy rotation. No config headaches. Just results.

‍

‍