Airline fare and availability data without a browser

Fare and availability searches are short-lived and repeated constantly, which makes browser rendering the most expensive way to run them. Clear the bot manager once per session and send the searches as API calls.

What gets in the way

Akamai in front of the search

Akamai Bot Manager is common in front of airline and travel booking sites. The search endpoint refuses sessions that have not cleared it.

Searches are many and small

One route and date is one request, and a fare calendar is hundreds. Per-search browser rendering turns a cheap query into seconds of CPU.

Sessions expire mid-run

Long search runs outlive a clearance. A job that does not notice starts collecting block pages instead of fares.

Which solver applies

Pick by what the site sends back. Send the wrong type and the solver refuses instead of guessing, at no charge.

Akamai SBSD solver

  • When the booking page loads an sbsd challenge script.
from €1.00€2.50 before level discounts

Akamai edge solver

  • When the first request is screened on headers and TLS.
from €1.00€2.50 before level discounts

How a job runs

  1. Open a session on the site’s search page with a Chrome-like client and a sticky residential IP.
  2. Clear the edge screen or the sbsd challenge if one is served.
  3. Send the fare searches on that session as ordinary requests.
  4. Watch for a challenge in the responses, solve again when it appears, and carry on.

What keeps it working

Detect the challenge, do not guess

Check each response for the challenge script or a block status and solve on demand. Solving on a timer wastes money and still misses expiries.

Spread searches across sessions

Several sessions at a moderate rate last longer than one session at a high rate.

Match language and timezone

For sbsd, set the language and timezone fields to what your client sends, so the browser description agrees with your requests.

Questions

Is this faster than a headless browser?

The sbsd solve takes about a second and the searches themselves are plain HTTP requests, so the time per search is the site’s own response time.

What if the site uses Akamai sensor data?

That is a separate Akamai mechanism and its solver is not live yet. The sbsd challenge and the edge screen are.

Do you store the fares or my proxy?

No. You make the searches yourself. For the edge solver, your proxy is used for that one request and is not stored with your usage records.

Solvers

Page updated .

Try it on your own target.

Login, copy a key, send one request. If the solve fails, it costs you nothing.

Airline fare and availability data, no browser | notabot