Fares and rates from every point of sale

Collect flight fares, hotel rates and availability the way travellers in each country see them, through residential and mobile IPs in 249 countries and territories.

A flight route with fares changing along the way

Why fare collection breaks

Travel sites protect their search hardest, and price by the traveller's country. A datacenter request is refused before it sees a fare.

From a datacenter
$ curl -i "https://fares.example/api/search?from=LHR&to=JFK&date=2026-12-18"
HTTP/2 403
content-type: application/json
{"error": "access_denied"}
Fails: No fare for this route today, and the price history has a gap.
Through 2extract, UK
$ curl -i -x http://…-country-gb@proxy.2extract.net:5555 \
"https://fares.example/api/search?from=LHR&to=JFK&date=2026-12-18"
HTTP/2 200
content-type: application/json
{"currency": "GBP", "fares": [
{"flight": "XY 117", "total": 412.30}, …
Works: A residential IP in the UK gets the fares a UK traveller is offered, in pounds.

From sign-up to the first fare

One endpoint for every point of sale: the country travels in the username.

  1. Create an account and add funds

    Sign up with Google, GitHub or email and top up from $10.

  2. Pick the point of sale

    Add -country-<code> for the market whose prices you need; use mobile IPs for app-only fares.

  3. Keep each search on one IP

    A sticky session with -session-<id> keeps the search, the results and the price check together.

# Replace with your credentials from the 2extract dashboard
curl --proxy "http://2xt-customer-[accountID]-proxy-[name]-[params]:proxy_password@proxy.2extract.net:5555" \
  "https://api.ipify.org?format=json"
View full documentation

What travel data needs from the network

Every setting is a username parameter or an API call, so each search runs from the market it prices.

What travel data needs from the network

  • Every point of sale

    249 countries and territories, so fares come in each market's currency and rules.

  • Sessions for search flows

    A sticky session holds one IP from the search to the fare details.

  • Mobile for app fares

    Mobile IPs for the prices travel apps show phone users.

Collect fares in any market: pay per GB from $3.99, no commitment

Travel data questions

Targeting and sessions are in the documentation.

Still have a question?

Talk directly to the engineers who built the product. No chatbots, no first-level support scripts.

Your first fare is one line away

Sign up with Google, GitHub or email, top up from $10 and pay per GB. No commitment.

curl -x http://…-country-gb:•••@proxy.2extract.net:5555 ipinfo.io/json