Use cases
Fare data, and why this is the hardest thing on this list
Travel is where a plain fetch API meets its limits fastest. Fares are generated per query, the queries multiply, and the industry defends its search endpoints harder than almost anyone else. This page is mostly about what fails, because that is the useful part.
What we do not offer
No GDS or NDC connectivity, no airline or agency partner feeds, and no booking of any kind — we return responses and never transact. No headless browser, no CAPTCHA solving, no POST to targets and no session handling. No currency normalisation or fare parsing either: whatever the page said is what you get.
A fare is a function, not a page
A price on a shelf has one URL. A fare does not: it is the output of origin, destination, date, return date, cabin, passenger mix and how far ahead you are asking. Every combination you want to know is a separate request, and the combinations multiply.
Twenty routes across sixty departure dates checked once a day is twelve hundred requests a day. Add a return date and it is not twelve hundred any more. The first design decision in fare collection is always which slice of the search space you can justify, not how fast you can poll it.
Most fare search is a POST behind a session
Our fetch takes a URL and performs a GET. No request body toward the target, no cookies, no headers beyond User-Agent, and no JavaScript execution. Airline and agency search almost always involves at least one of those: a form POST, a session token minted on page load, or a client-side call to an internal endpoint that expects headers we do not send.
So say it plainly: if the fare only exists after a form submission or a browser has run code, we cannot reach it. No proxy fixes that, because it is not an address problem.
What does work
The reachable part of this domain is real, just narrower than the brochure version.
Query-string search URLs
Where a site encodes the whole search in the URL and answers a plain GET, a fetch works and the URL is your query.
Published tariffs and fee tables
Baggage charges, seat fees, change and cancellation terms, usually static pages that change a few times a year.
Schedules and timetables
Rail and coach operators and many transit authorities publish timetable data as documents on public URLs.
Public rate and availability pages
Some accommodation and rental sites still answer a plain GET with rates rendered server-side.
Where the region parameter earns its keep
Travel pricing varies by where the request appears to come from more than almost any other category — currency, point of sale, which promotions render, sometimes a different fare entirely. Fetching the same URL with region=us-east and region=europe is the cheapest way to see that difference, and region_used records which region actually served each copy.
We run three regions. If your comparison needs a point of sale in Asia-Pacific, the Middle East or South America, we do not have an exit there and the request will fail fast rather than be served from the wrong continent.
Before you build
Pick five URLs that represent the hardest thing you need and try them. You will know within an afternoon whether your targets answer a GET, and that is a far better basis for a decision than any claim on a marketing page. If they do not answer, tell us what you were aiming at — we would rather lose the deal early than take money for a workload we cannot serve.
Questions
- Can you get fares out of an airline's own search?
- Only if that search runs on a plain GET URL and renders server-side. Most do not. Test your specific targets before you commit to anything; the answer is target by target, not a general capability we can promise.
- Does choosing a region change the currency I see?
- Often, yes — many travel sites set point of sale and currency from the requesting address. That is a reason to fetch the same URL from more than one region rather than to trust one of them.
- Can the API make a booking for me?
- No. The proxy performs a GET and returns what came back. It does not submit forms, hold inventory or complete transactions of any kind.
Get a key
Create an account and mint an API key in the dashboard. The full endpoint reference — request shapes, parameters and error codes — is published at https://api.roamingproxy.com/v2/docs.