Air France is half of one of Europe's biggest airline groups, and like its group partner it prices by where you appear to be buying. AF-KLM files fares by point of sale, quotes them in the local market's currency, and defends its site with the same Akamai-class bot management as the other majors, so reading an Air France fare accurately means appearing to be a traveler in the market whose price you want. Proxies for Air France are the tool for reading those market-specific fares the way a local traveler sees them, on a schedule, from connections the site treats as ordinary.
We run a proxy network, and Air France traffic reaches us from fare trackers, corporate travel teams and travel-data teams. This page covers what is specific to Air France: point-of-sale pricing across the AF-KLM group, how the site blocks, which proxy type fits and how to size it. The group's German counterpart with the clearest distribution story is proxies for Lufthansa, the metasearch that carries these fares is proxies for Skyscanner, and the sector background is in travel fare aggregation.
What proxies are best for Air France?
Rotating residential proxies driven by a real browser, pinned to the country of sale you want, with a static residential (ISP) exit for Flying Blue account work. Air France files fares by point of sale and runs Akamai-class defenses, so a home connection in the right country is both the accuracy rule and the reputation rule. Keep a mobile exit for the rare run that keeps getting flagged.
Point of sale, across the group
The Air France mechanic is the European one, and it applies across the AF-KLM group. Air France and KLM, run as one group with the shared Flying Blue loyalty program, file fares by point of sale, the market a booking appears to originate from, and quote them in that market's currency with that market's taxes. So the same seat can cost noticeably more or less depending on the country the request comes from, and Flying Blue redemption and cash-plus-miles options can vary by market too.
The practical consequence for a data team is direct: to read the fare a traveler in a given country sees, the request has to exit from that country. A German price wants a German residential exit, a French one a French exit, and a datacenter address wearing a country label collects a generic page in the wrong currency, because the airline weighs where the network truly sits over the tag attached to it. Reading the AF-KLM group properly is reading each market from an in-country exit, the same discipline we describe for Lufthansa.
Fare filed by point of sale
the market of purchase
Local currency and taxes
set by the market
Exit from that country
residential IP
The real local fare
what a traveler there sees
How Air France blocks you
Air France defends its fare search with Akamai-class bot management, the same defense reported on the US majors and Lufthansa. Akamai builds a trust score from the TLS handshake (the JA3/JA4 fingerprint taken from the ClientHello before any HTTP is sent), the JavaScript environment and behavioral signals, and it challenges or blocks a client that looks automated before the fare engine answers (ScrapingBee, Python flight scraper). The fares load with JavaScript into a near-empty shell, so a plain fetch returns no prices. The rule is the shared one: a residential address with a decent trust score, and a real browser whose handshake matches a human.
Which proxy type fits: residential, datacenter, ISP, or mobile
Datacenter proxies fail the trust score first and misread the point of sale. They belong to parser development on saved pages.
Rotating residential proxies are home connections from a pool, one per search, rotated, pinned to the country of sale, and they carry the trust score that clears Akamai when paired with a real browser (background in what is a residential proxy).
ISP proxies are static residential addresses for Flying Blue sessions.
Mobile proxies are carrier IPs many handsets share, kept for the hardest runs.
| Air France job | Proxy type | Why |
|---|---|---|
| Fare tracking across markets | Rotating residential, country-of-sale pinned | Point of sale plus Akamai trust score |
| Flying Blue account actions | ISP (static residential) | Session and account on one address |
| Runs that keep getting challenged | Mobile | Carrier ranges carry high trust |
| Parser development | Datacenter or free list | Saved pages, nothing at stake |
Free versus paid for Air France
A free proxy is a shared datacenter address, exactly what Akamai rejects first, and it reads the wrong point of sale on top of that. For a single manual look at one market, our free proxy list and proxy checker cost nothing. For a tracker across markets, paid residential behind a real browser is the floor at $0.44/GB pay-as-you-go, no KYC.
Setting it up
Render with a real browser behind a residential exit pinned to the country of sale (Playwright, Puppeteer), and let the country site choose its currency. Read each route across the markets you care about, one exit per market, and record the market, currency and timestamp on every fare. Rotate one IP per search and hold a sticky ISP exit for Flying Blue work; the split is in rotating vs static residential proxies.
How many IPs, and how fast
Sizing (rotating residential, one refresh cycle):
searches/cycle = routes x dates x markets
= 200 x 60 x 3 = 36,000 searches
per search = a browser render behind Akamai
per address = a few searches, then rotate
Refresh near-term dates daily, far dates weekly. The pool spreads it.
Our pricing is per gigabyte with no expiry, so a multi-market tracker pays for the markets it reads.
Staying unblocked on Air France
- Residential IP in the country of sale, plus a real browser. Accuracy and Akamai in one rule.
- Guard the handshake. The TLS fingerprint is Akamai's top vector.
- One search per address, then rotate.
- Record market and currency with every fare.
- Back off on the first challenge. The checklist is in avoiding IP bans while scraping.
The limits worth knowing
Proxies put an Air France read on the right point of sale on a trusted connection and spread a tracker so the site sees travelers. They do not clear Akamai alone, because the client half of the score is on you, and they do not change AF-KLM's terms of service. Read per market, drive a real browser, and the group's fares line up with the rest of the sector.
A single manual read is free on our free proxy list and proxy checker. For a multi-market fare tracker, rotating residential at $0.44/GB pay-as-you-go behind a real browser, pinned to the country of sale, is what reads Air France.
Sources
- ScrapingBee, how to build a Python flight scraper, on Akamai Bot Manager, JA3/JA4 and the JavaScript shell.
- HProxy, proxies for Lufthansa, for the European point-of-sale pricing that applies to the AF-KLM group too.