<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Matan Rabi</title>
    <description>The latest articles on DEV Community by Matan Rabi (@matanrabi).</description>
    <link>https://dev.to/matanrabi</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4106861%2F9ed924bf-73b8-4d8d-82dd-07204e1e196d.jpg</url>
      <title>DEV Community: Matan Rabi</title>
      <link>https://dev.to/matanrabi</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/matanrabi"/>
    <language>en</language>
    <item>
      <title>I checked Google Flights' calendar prices against full searches, and 10 of 10 matched</title>
      <dc:creator>Matan Rabi</dc:creator>
      <pubDate>Thu, 19 Nov 2026 07:08:25 +0000</pubDate>
      <link>https://dev.to/matanrabi/i-checked-google-flights-calendar-prices-against-full-searches-and-10-of-10-matched-1pj5</link>
      <guid>https://dev.to/matanrabi/i-checked-google-flights-calendar-prices-against-full-searches-and-10-of-10-matched-1pj5</guid>
      <description>&lt;p&gt;I build a small Google Flights API, and this week I wanted to settle one question. When Google's date calendar says a trip costs $627 on a given day, does a real search for that day agree?&lt;/p&gt;

&lt;p&gt;It matters because the calendar is the cheap read. One request gives you a whole month of prices, while a full search prices one date pair at a time and takes longer (in my runs today the month took 1 to 5 seconds, a single full round-trip search 5 to 32 seconds). If the calendar holds up, you scan with it and only run the full search on the date you actually pick.&lt;/p&gt;

&lt;h2&gt;
  
  
  The test
&lt;/h2&gt;

&lt;p&gt;Three round trips in March 2027, one adult, prices in USD:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;New York JFK to Lisbon, 7 nights&lt;/li&gt;
&lt;li&gt;London Heathrow to Barcelona, 4 nights&lt;/li&gt;
&lt;li&gt;Los Angeles to Mexico City, 5 nights&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For each route I read the calendar for the whole month (31 departure dates, all 31 came back priced), then ran a full round-trip search on three of those dates: the cheapest, one from the middle and the most expensive. I had already checked one extra JFK to Lisbon date while testing the call, so that's 10 checks. Everything ran on 19 November 2026 between 07:02 and 07:05 UTC.&lt;/p&gt;

&lt;h2&gt;
  
  
  The result
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Route&lt;/th&gt;
&lt;th&gt;Calendar, whole month&lt;/th&gt;
&lt;th&gt;Date checked&lt;/th&gt;
&lt;th&gt;Calendar&lt;/th&gt;
&lt;th&gt;Full search&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;JFK → LIS, 7 nights&lt;/td&gt;
&lt;td&gt;$627 to $747&lt;/td&gt;
&lt;td&gt;Mar 1 → Mar 8&lt;/td&gt;
&lt;td&gt;$627&lt;/td&gt;
&lt;td&gt;$627&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;Mar 3 → Mar 10&lt;/td&gt;
&lt;td&gt;$627&lt;/td&gt;
&lt;td&gt;$627&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;Mar 15 → Mar 22&lt;/td&gt;
&lt;td&gt;$716&lt;/td&gt;
&lt;td&gt;$716&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;Mar 20 → Mar 27&lt;/td&gt;
&lt;td&gt;$747&lt;/td&gt;
&lt;td&gt;$747&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;LHR → BCN, 4 nights&lt;/td&gt;
&lt;td&gt;$83 to $285&lt;/td&gt;
&lt;td&gt;Mar 8 → Mar 12&lt;/td&gt;
&lt;td&gt;$83&lt;/td&gt;
&lt;td&gt;$83&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;Mar 19 → Mar 23&lt;/td&gt;
&lt;td&gt;$132&lt;/td&gt;
&lt;td&gt;$132&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;Mar 25 → Mar 29&lt;/td&gt;
&lt;td&gt;$285&lt;/td&gt;
&lt;td&gt;$285&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;LAX → MEX, 5 nights&lt;/td&gt;
&lt;td&gt;$289 to $367&lt;/td&gt;
&lt;td&gt;Mar 1 → Mar 6&lt;/td&gt;
&lt;td&gt;$289&lt;/td&gt;
&lt;td&gt;$289&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;Mar 6 → Mar 11&lt;/td&gt;
&lt;td&gt;$334&lt;/td&gt;
&lt;td&gt;$334&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;Mar 28 → Apr 2&lt;/td&gt;
&lt;td&gt;$367&lt;/td&gt;
&lt;td&gt;$367&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;All 10 matched to the dollar. "Full search" here is the cheapest of the rows the round-trip search returned for that exact date pair.&lt;/p&gt;

&lt;p&gt;The other thing the table shows is why it's worth scanning at all: London to Barcelona went from $83 to $285 inside one month, more than three times the price for the same 4-night trip.&lt;/p&gt;

&lt;p&gt;A few honest notes before anyone builds on this:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;10 checks, on busy routes, a few minutes after reading the calendar. Fares move during the day, so the longer you wait between the calendar and the search, the more room there is for a gap. I'd always confirm the date before showing someone a price.&lt;/li&gt;
&lt;li&gt;The calendar is a number per date and nothing else: no airline, no times, no stops. The full search has all of that (the $627 JFK to Lisbon trip on March 3 was a TAP / JetBlue nonstop).&lt;/li&gt;
&lt;li&gt;I only tested adults. A party with children prices differently and I left it out of this run.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The call
&lt;/h2&gt;

&lt;p&gt;One request for the whole month. This is the shape of it on RapidAPI:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl -X POST &lt;span class="s2"&gt;"https://google-flights-live-api.p.rapidapi.com/api/google_flights/cheapest_dates/v1"&lt;/span&gt; \
  -H &lt;span class="s2"&gt;"Content-Type: application/json"&lt;/span&gt; \
  -H &lt;span class="s2"&gt;"x-rapidapi-host: google-flights-live-api.p.rapidapi.com"&lt;/span&gt; \
  -H &lt;span class="s2"&gt;"x-rapidapi-key: $RAPIDAPI_KEY"&lt;/span&gt; \
  -d &lt;span class="s1"&gt;'{"from_airport":"JFK","to_airport":"LIS","month":"2027-03","nights":7,"currency":"USD"}'&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;And what came back for JFK to Lisbon (first 3 of 31 dates):&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nl"&gt;"from_airport"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"JFK"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"to_airport"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"LIS"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"trip_type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"roundtrip"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"nights"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;7&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"adults"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"currency"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"USD"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"fetched_at"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"2026-11-19T07:02:12Z"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"dates_searched"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;31&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"dates_with_price"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;31&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"cheapest"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"departure_date"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"2027-03-01"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nl"&gt;"return_date"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"2027-03-08"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nl"&gt;"price"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mf"&gt;627.0&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"dates"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;
    &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"departure_date"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"2027-03-01"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nl"&gt;"return_date"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"2027-03-08"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nl"&gt;"price"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mf"&gt;627.0&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"departure_date"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"2027-03-02"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nl"&gt;"return_date"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"2027-03-09"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nl"&gt;"price"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mf"&gt;679.0&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"departure_date"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"2027-03-03"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nl"&gt;"return_date"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"2027-03-10"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nl"&gt;"price"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mf"&gt;627.0&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
  &lt;span class="p"&gt;]&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Drop &lt;code&gt;nights&lt;/code&gt; and you get a one-way calendar instead. You can also send &lt;code&gt;departure_date_from&lt;/code&gt; / &lt;code&gt;departure_date_to&lt;/code&gt; for any range up to 61 days instead of a month.&lt;/p&gt;

&lt;h2&gt;
  
  
  Scan with the calendar, confirm with a full search
&lt;/h2&gt;

&lt;p&gt;This is the whole pattern in a few lines of Node (18+, built-in &lt;code&gt;fetch&lt;/code&gt;):&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="no"&gt;HOST&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="s2"&gt;"google-flights-live-api.p.rapidapi.com"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;headers&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="s2"&gt;"Content-Type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"application/json"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="s2"&gt;"x-rapidapi-host"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="no"&gt;HOST&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="s2"&gt;"x-rapidapi-key"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nb"&gt;process&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;env&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="no"&gt;RAPIDAPI_KEY&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="k"&gt;async&lt;/span&gt; &lt;span class="kd"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;post&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;path&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;body&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;res&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nb"&gt;fetch&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sb"&gt;`https://${HOST}${path}`&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="n"&gt;method&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"POST"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="n"&gt;headers&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="n"&gt;body&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nb"&gt;JSON&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;stringify&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;body&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="o"&gt;!&lt;/span&gt;&lt;span class="n"&gt;res&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;ok&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;throw&lt;/span&gt; &lt;span class="k"&gt;new&lt;/span&gt; &lt;span class="nb"&gt;Error&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sb"&gt;`${path} answered ${res.status}`&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="n"&gt;res&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;json&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="c1"&gt;// 1. One request: the whole month&lt;/span&gt;
&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;cal&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nf"&gt;post&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"/api/google_flights/cheapest_dates/v1"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="n"&gt;from_airport&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"JFK"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="n"&gt;to_airport&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"LIS"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="n"&gt;month&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"2027-03"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="n"&gt;nights&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;7&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="n"&gt;currency&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"USD"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;departure_date&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;return_date&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;price&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;cal&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;cheapest&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="nb"&gt;console&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;log&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sb"&gt;`Calendar says ${departure_date} -&amp;gt; ${return_date} at $${price}`&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="c1"&gt;// 2. One more request: the full search for that date pair only&lt;/span&gt;
&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;rows&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nf"&gt;post&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"/api/google_flights/roundtrip/v1"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="n"&gt;from_airport&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"JFK"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="n"&gt;to_airport&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"LIS"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="n"&gt;departure_date&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="n"&gt;return_date&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="n"&gt;currency&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"USD"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;best&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;rows&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;reduce&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;a&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;b&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt;
  &lt;span class="n"&gt;b&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;total_price_as_number&lt;/span&gt; &lt;span class="o"&gt;&amp;lt;&lt;/span&gt; &lt;span class="n"&gt;a&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;total_price_as_number&lt;/span&gt; &lt;span class="o"&gt;?&lt;/span&gt; &lt;span class="n"&gt;b&lt;/span&gt; &lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;a&lt;/span&gt;
&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="nb"&gt;console&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;log&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
  &lt;span class="sb"&gt;`Full search: $${best.total_price_as_number}, `&lt;/span&gt; &lt;span class="o"&gt;+&lt;/span&gt;
  &lt;span class="sb"&gt;`${best.departure_flight_airline}, ${best.total_stops} stops`&lt;/span&gt;
&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="nb"&gt;console&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;log&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;best&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;buy_link&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Two requests instead of 31, and the second one gives you the airline, the times and a link to book.&lt;/p&gt;

&lt;p&gt;If the two prices ever disagree, trust the full search: it's the one that reflects the actual flights on sale right now.&lt;/p&gt;




&lt;p&gt;Disclosure: I built the API used here (FlightPowers), and the &lt;a href="https://flightpowers.com/flights-api/cheapest-dates" rel="noopener noreferrer"&gt;docs for the cheapest dates endpoint&lt;/a&gt; have the full field list and error codes. An AI agent I run wrote and published this post, and the numbers in it come from the calls described above, which I saved as raw responses.&lt;/p&gt;

</description>
      <category>api</category>
      <category>travel</category>
      <category>javascript</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Only 36% of flight searches on my demo had fixed dates</title>
      <dc:creator>Matan Rabi</dc:creator>
      <pubDate>Thu, 22 Oct 2026 16:23:11 +0000</pubDate>
      <link>https://dev.to/matanrabi/only-36-of-flight-searches-on-my-demo-had-fixed-dates-2acl</link>
      <guid>https://dev.to/matanrabi/only-36-of-flight-searches-on-my-demo-had-fixed-dates-2acl</guid>
      <description>&lt;p&gt;I counted a year of searches on my flight search demo, and only 36% of them had fixed dates.&lt;/p&gt;

&lt;p&gt;I build FlightPowers, a flight and hotel price API. The demo at demo.flightpowers.com lets you write something like "cheap flight to Europe sometime in October, 3-4 nights" and get live fares back. Between April 2025 and March 2026 the engine ran 27,320 searches there. About 4,900 signed-in users ran 21,822 of them, and visitors who weren't signed in ran the rest (most searches started in Tel Aviv).&lt;/p&gt;

&lt;h2&gt;
  
  
  How I counted
&lt;/h2&gt;

&lt;p&gt;The database keeps the structured search the model turned each prompt into (origins, destinations, the date window, nights, stops, sort), never the prompt text. I grouped everything in SQL and never exported a row. Any group with fewer than 20 people stays out of this post.&lt;/p&gt;

&lt;p&gt;One prompt can fan out into a couple of searches, about 1.5 per ask when you count one ask per signed-in user per minute, so "searches" below means searches the engine ran.&lt;/p&gt;

&lt;p&gt;Right now the data covers one site, and over half of it comes from a busy August and September 2025.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Most searches didn't pin the dates
&lt;/h2&gt;

&lt;p&gt;Only 36% of searches had fixed dates. The other 64% left room in the departure date or the length of stay, and nearly a third of all searches left more than two weeks.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fgxzsxptgk5g5ofn9u8ki.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fgxzsxptgk5g5ofn9u8ki.png" alt="64% of flight searches left room in the dates" width="800" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Nearly one in ten searches listed 10+ airports
&lt;/h2&gt;

&lt;p&gt;71% had a single destination airport. But 9.5% listed 10 or more, and since the prompt isn't stored, my guess is a lot of those were "anywhere cheap" asks.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Thursday
&lt;/h2&gt;

&lt;p&gt;When the dates were fixed, 32% of searches asked to leave on a Thursday, 1.8 times Friday's share. Most searches on the site start in Tel Aviv, where the weekend is Friday and Saturday, so my guess is Thursday after work.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fsuw0psf2lap1kn1y02mp.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fsuw0psf2lap1kn1y02mp.png" alt="32% of fixed-date searches were for a Thursday departure" width="800" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Short trips, about 40 days ahead
&lt;/h2&gt;

&lt;p&gt;38% of round-trip searches set their shortest stay at 3-4 nights, and the median search looked about 40 days ahead.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Bangkok and New York
&lt;/h2&gt;

&lt;p&gt;In searches from Tel Aviv that named a single city, Bangkok drew the most people (about 290), then New York (about 260), and both beat every European city. European cities still fill the top of the overall count, mostly through searches that listed several cities.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F2wvhwqhyidm5bds6tcig.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F2wvhwqhyidm5bds6tcig.png" alt="About 290 people ran a Bangkok-only search from Tel Aviv" width="800" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What it means if you build flight search
&lt;/h2&gt;

&lt;p&gt;When most searches carry a range, one search is really many API requests. A 31-day month with 3 cities and 3 stay lengths is already 279 requests (31 × 3 × 3).&lt;/p&gt;

&lt;p&gt;That's what I built FlightPowers around. A round trip is one request, with both legs priced together and one total. Over REST you fan the dates out yourself, and the 10$ PRO plan allows 150 requests a minute, so those 279 requests take about two minutes. With a RapidAPI key, the MCP server (Claude, ChatGPT or Cursor) takes a date range and a list of destinations in one call, up to 300 billed combinations.&lt;/p&gt;

&lt;p&gt;You can try it free from Claude with ads (free-trial.flightpowers.com/mcp, Google sign-in, 50 searches a day), and PRO is 10$ for 2,500 requests a month with a RapidAPI key: &lt;a href="https://rapidapi.com/mtnrabi/api/google-flights-live-api" rel="noopener noreferrer"&gt;https://rapidapi.com/mtnrabi/api/google-flights-live-api&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Which do you search with more often, fixed dates or a range? :)&lt;/p&gt;

</description>
      <category>api</category>
      <category>datascience</category>
      <category>travel</category>
      <category>ai</category>
    </item>
    <item>
      <title>I benchmarked seven hotel price APIs on the same Rome room, and the prices were 16% apart because of tax</title>
      <dc:creator>Matan Rabi</dc:creator>
      <pubDate>Wed, 07 Oct 2026 14:52:15 +0000</pubDate>
      <link>https://dev.to/matanrabi/i-benchmarked-seven-hotel-price-apis-on-the-same-rome-room-and-the-prices-were-16-apart-because-3480</link>
      <guid>https://dev.to/matanrabi/i-benchmarked-seven-hotel-price-apis-on-the-same-rome-room-and-the-prices-were-16-apart-because-3480</guid>
      <description>&lt;p&gt;I run FlightPowers, a small API that reads live Booking.com rates, so I'm biased about one row of this table. I wanted to know how it holds up next to the APIs people usually compare it with, so I spent an afternoon sending them all the same questions and kept every response.&lt;/p&gt;

&lt;h2&gt;
  
  
  The setup
&lt;/h2&gt;

&lt;p&gt;Same stay for everyone: check-in 2026-11-20, check-out 2026-11-23, 2 adults, 1 room, USD. Three questions, three runs each, median wall time from one server in the US:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;A destination search for Lisbon, sorted by price where the API can sort.&lt;/li&gt;
&lt;li&gt;One named hotel: Hotel Artemide in Rome. (I started with Hotel Sant'Angelo, but it was sold out on Booking.com for those dates.)&lt;/li&gt;
&lt;li&gt;That same hotel seen from Germany and from the US, where the API has an input for it.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Free tiers only. SerpApi got &lt;code&gt;no_cache=true&lt;/code&gt;, because its default hands back an identical search from cache for an hour and that would have flattered its time.&lt;/p&gt;

&lt;h2&gt;
  
  
  Speed and sorting
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;API (source)&lt;/th&gt;
&lt;th&gt;Lisbon search, median&lt;/th&gt;
&lt;th&gt;sorts by price&lt;/th&gt;
&lt;th&gt;one named hotel&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;StayAPI (Booking.com)&lt;/td&gt;
&lt;td&gt;1.1 s&lt;/td&gt;
&lt;td&gt;no&lt;/td&gt;
&lt;td&gt;2 calls: ID lookup, then prices (2.5 s for the prices call)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;SearchApi (Booking.com)&lt;/td&gt;
&lt;td&gt;1.9 s&lt;/td&gt;
&lt;td&gt;yes&lt;/td&gt;
&lt;td&gt;room list in 2 calls: search for the URL, then the property (3.0 s for that call)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;HasData (Booking.com)&lt;/td&gt;
&lt;td&gt;2.1 s&lt;/td&gt;
&lt;td&gt;yes&lt;/td&gt;
&lt;td&gt;room list in 2 calls: search for the URL, then the place (3.2 s for that call)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;SerpApi (Google Hotels)&lt;/td&gt;
&lt;td&gt;2.4 s&lt;/td&gt;
&lt;td&gt;yes&lt;/td&gt;
&lt;td&gt;1 call by name (2.5 s)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;FlightPowers, mine (Booking.com)&lt;/td&gt;
&lt;td&gt;7.9 s&lt;/td&gt;
&lt;td&gt;no&lt;/td&gt;
&lt;td&gt;1 call by name (10.2 s)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Apify voyager/booking-scraper&lt;/td&gt;
&lt;td&gt;75 s with actor start&lt;/td&gt;
&lt;td&gt;asked, rows came back unsorted&lt;/td&gt;
&lt;td&gt;1 run by name (39 s, one run)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Xotelo (TripAdvisor rates)&lt;/td&gt;
&lt;td&gt;0.7 s, but the list takes no dates&lt;/td&gt;
&lt;td&gt;n/a&lt;/td&gt;
&lt;td&gt;by TripAdvisor key (0.7 s)&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Mine is the slow one. It loads the page in a real browser through a residential proxy for every call, and you pay for that in seconds. It also has no price sort yet: I sent &lt;code&gt;"sort": "price"&lt;/code&gt; and it was accepted and ignored, which is a bug on my list.&lt;/p&gt;

&lt;p&gt;SearchApi's and HasData's search take a hotel name too (SearchApi put Hotel Sant'Angelo first when I searched it by name), so one row price for a named hotel is a single call there as well. Their second call is for the full room list.&lt;/p&gt;

&lt;h2&gt;
  
  
  One room, two prices
&lt;/h2&gt;

&lt;p&gt;Hotel Artemide, Basic Double, those three nights. Here is what each API called the price:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;where the number came from&lt;/th&gt;
&lt;th&gt;what came back&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;HasData&lt;/td&gt;
&lt;td&gt;$914.64 + $142.12 tax = $1,056.76&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;StayAPI, US market&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;total_price&lt;/code&gt; $914.64, tax listed as not included&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;StayAPI, German market&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;total_price&lt;/code&gt; $1,061.71, tax listed as included&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;SearchApi&lt;/td&gt;
&lt;td&gt;$915, no tax field on the room rows&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;FlightPowers, &lt;code&gt;proxy_country=us&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;$1,057, three runs out of three&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Same rate underneath. Booking.com shows a US visitor the room before tax and adds 10% VAT and the Rome city tax at the end. The German view folds them into the price. So the number you store depends on which field an API calls the price and which market it read from. StayAPI's &lt;code&gt;total_price&lt;/code&gt; means before tax in one market and after tax in the other, for the same room. Its docs warn that the market changes tax display, and the tax breakdown says which way it went, so you can fix it if you read it.&lt;/p&gt;

&lt;p&gt;If you load hotel rates into anything that compares sources or countries, normalise to the tax-inclusive total first. Otherwise a 16% "price gap" shows up that's only accounting.&lt;/p&gt;

&lt;p&gt;Two smaller ones. The cheapest Lisbon row on SearchApi and on HasData was the same hostel bunk ($51 before tax, $81 after). And the Apify scraper's cheapest result was one bed in a 10-bed dorm priced for one person, on a search for two adults.&lt;/p&gt;

&lt;h2&gt;
  
  
  Does the country change the rate?
&lt;/h2&gt;

&lt;p&gt;A little, on this hotel. StayAPI's before-tax figure was $919.14 from Germany and $914.64 from the US. Mine, tax included both times, read $1,028 from Germany on two of three runs and $1,057 from the US on all three. Without a pinned country mine moves more ($935, $1,011 and $1,062 for the Basic Double on three calls to the room list), because each call can leave from a different country's residential IP. Pinning helps but doesn't settle it: the Germany runs still read $1,062 once and $1,028 twice.&lt;/p&gt;

&lt;h2&gt;
  
  
  What it costs at the entry plan
&lt;/h2&gt;

&lt;p&gt;Read from each vendor's pricing page the same afternoon:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;HasData: a Booking.com call is 10 credits, so about $0.003 a call on the $59 plan (200,000 credits)&lt;/li&gt;
&lt;li&gt;SearchApi: $0.004 ($40 for 10,000), 100 free requests once&lt;/li&gt;
&lt;li&gt;FlightPowers: $0.005 ($10 for 2,000), 10 free a month&lt;/li&gt;
&lt;li&gt;SerpApi: $0.025, their cheapest plan is $25 for 1,000, 250 free a month&lt;/li&gt;
&lt;li&gt;StayAPI: $0.033 ($49 for 1,500), 50 free requests once&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;So two of them are cheaper per call than mine. What mine has is the $10 entry and one tax-inclusive total from a country you pick.&lt;/p&gt;

&lt;h2&gt;
  
  
  Caveats
&lt;/h2&gt;

&lt;p&gt;One afternoon, one server, three runs a query. Google Hotels is a metasearch across sellers (34 of them for Artemide), so SerpApi's Lisbon list isn't the same set of hotels as the Booking.com APIs. Makcorps isn't in the timings because its sign-up wanted a username and password and I stuck to Google sign-ins, and the Booking.com Demand API needs a partner contract.&lt;/p&gt;

&lt;p&gt;The full write-up, with every price source and the per-call timings, is on &lt;a href="https://flightpowers.com/guides/hotel-rates-api-benchmark-2026" rel="noopener noreferrer"&gt;the benchmark page&lt;/a&gt;. I'll rerun it next month. If you store hotel prices somewhere, I'm curious whether you keep the before-tax number with tax in its own column, or the total.&lt;/p&gt;

</description>
      <category>api</category>
      <category>webdev</category>
      <category>benchmark</category>
      <category>travel</category>
    </item>
    <item>
      <title>I benchmarked four Google Flights APIs on the same searches, and the fares matched to the dollar</title>
      <dc:creator>Matan Rabi</dc:creator>
      <pubDate>Wed, 07 Oct 2026 14:50:55 +0000</pubDate>
      <link>https://dev.to/matanrabi/i-benchmarked-four-google-flights-apis-on-the-same-searches-and-the-fares-matched-to-the-dollar-30pb</link>
      <guid>https://dev.to/matanrabi/i-benchmarked-four-google-flights-apis-on-the-same-searches-and-the-fares-matched-to-the-dollar-30pb</guid>
      <description>&lt;p&gt;I sell a Google Flights API (FlightPowers), and I wanted a real answer to how it compares to SerpApi, SearchApi and HasData. So I ran the same three searches through all four in the same hour on 7 October 2026 and timed every call.&lt;/p&gt;

&lt;p&gt;Disclosure up front: I built one of the four rows. The method, the places where mine loses and the timing of every single call are public on the &lt;a href="https://flightpowers.com/guides/flight-api-benchmark-2026" rel="noopener noreferrer"&gt;benchmark page&lt;/a&gt;, and I'll re-run it every month.&lt;/p&gt;

&lt;h2&gt;
  
  
  The searches
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;A round trip, JFK to LHR, out 18 November, back 25 November.&lt;/li&gt;
&lt;li&gt;A one way, TLV to BKK on 3 December.&lt;/li&gt;
&lt;li&gt;A flexible scan, LHR to BCN, any departure from 10 to 16 November, 3 nights (seven date pairs).&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;One adult, economy, USD, three runs per search per API, from a VM in GCP us-central1. The time quoted is the median of the three runs, from sending the request to reading the last byte.&lt;/p&gt;

&lt;h2&gt;
  
  
  The results
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;FlightPowers (mine)&lt;/th&gt;
&lt;th&gt;SerpApi&lt;/th&gt;
&lt;th&gt;SearchApi&lt;/th&gt;
&lt;th&gt;HasData&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Cheapest fare, all three searches&lt;/td&gt;
&lt;td&gt;same&lt;/td&gt;
&lt;td&gt;same&lt;/td&gt;
&lt;td&gt;same&lt;/td&gt;
&lt;td&gt;same&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Round trip, both legs&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;3.27 s, 1 request&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;6.36 s, 2 requests&lt;/td&gt;
&lt;td&gt;4.29 s, 2 requests&lt;/td&gt;
&lt;td&gt;7.56 s, 2 requests&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;First round-trip price&lt;/td&gt;
&lt;td&gt;3.27 s&lt;/td&gt;
&lt;td&gt;2.26 s&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;1.98 s&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;5.23 s&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;One way&lt;/td&gt;
&lt;td&gt;1.56 s&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;1.34 s&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;1.50 s&lt;/td&gt;
&lt;td&gt;2.79 s&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;7-date scan, 7 calls in parallel&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;3.11 s&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;4.54 s&lt;/td&gt;
&lt;td&gt;28.37 s*&lt;/td&gt;
&lt;td&gt;15.99 s*&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Whole range in one call&lt;/td&gt;
&lt;td&gt;MCP server, bills 7&lt;/td&gt;
&lt;td&gt;no&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;calendar engine, bills 1&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;no&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Price history series&lt;/td&gt;
&lt;td&gt;no&lt;/td&gt;
&lt;td&gt;yes&lt;/td&gt;
&lt;td&gt;yes&lt;/td&gt;
&lt;td&gt;yes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Free tier&lt;/td&gt;
&lt;td&gt;10 a month&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;250 a month&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;100, once&lt;/td&gt;
&lt;td&gt;67 a month&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Entry plan&lt;/td&gt;
&lt;td&gt;$10 for 2,500&lt;/td&gt;
&lt;td&gt;$25 for 1,000&lt;/td&gt;
&lt;td&gt;$40 for 10,000&lt;/td&gt;
&lt;td&gt;$59 for 13,333&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Per 1,000 round trips with both legs&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;$4.00&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;$50.00&lt;/td&gt;
&lt;td&gt;$8.00&lt;/td&gt;
&lt;td&gt;$8.85&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;* One call took 16 to 28 seconds in two of the three runs (the median call was 1.9 s on SearchApi and 3.0 s on HasData, which ran 5 at a time on its trial account). A parallel scan waits for its slowest call.&lt;/p&gt;

&lt;h2&gt;
  
  
  The fares were identical
&lt;/h2&gt;

&lt;p&gt;All four returned $692 for the round trip, $619 for the one way and the same lowest price on each of the seven scan dates ($93 at the bottom, leaving Saturday 14 November), with the same Google price range. The only difference was a label: SearchApi called two of the seven scan dates "high" where the other three said "typical". That makes sense, since all four read the same Google Flights results, but it means nobody should pick one of these on "better prices".&lt;/p&gt;

&lt;h2&gt;
  
  
  The round trip is where they differ
&lt;/h2&gt;

&lt;p&gt;SerpApi, SearchApi and HasData answer a round trip with the outbound options, each priced as a round-trip total. The return flight is a second request with a &lt;code&gt;departure_token&lt;/code&gt;, and all three say so in their docs (quoted on the page). Mine pairs both legs in one request, which is why "both legs" is one request and 3.27 s here, and why a round trip with its return flight works out at $4.00 per 1,000 against $8.00 to $50.00.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl &lt;span class="nt"&gt;-X&lt;/span&gt; POST https://api.flightpowers.com/v1/flights/roundtrip &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;-H&lt;/span&gt; &lt;span class="s2"&gt;"x-api-key: &lt;/span&gt;&lt;span class="nv"&gt;$FLIGHTPOWERS_API_KEY&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt; &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;-H&lt;/span&gt; &lt;span class="s2"&gt;"Content-Type: application/json"&lt;/span&gt; &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;-d&lt;/span&gt; &lt;span class="s1"&gt;'{"from_airport":"JFK","to_airport":"LHR","departure_date":"2026-11-18","return_date":"2026-11-25","currency":"USD"}'&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Where mine loses
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;The first price.&lt;/strong&gt; SearchApi and SerpApi put a round-trip total on the table faster (1.98 s and 2.26 s against my 3.27 s). If you never need the return flight's details, they're quicker.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Every itinerary.&lt;/strong&gt; With &lt;code&gt;limit: 100&lt;/code&gt; my round trip took 15.68 s, since each extra outbound needs its own return-leg page.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The free tier.&lt;/strong&gt; Ten requests a month on the key. The bigger free path is the ad-supported MCP server (50 searches a day with a Google sign-in), which only helps if you use an MCP client.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Price history.&lt;/strong&gt; The other three return a &lt;code&gt;price_history&lt;/code&gt; series, and I return Google's band and its low, typical or high verdict only.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Date grids.&lt;/strong&gt; SearchApi's calendar engine prices every date pair for one billed search. My one-call scan bills one request per date pair.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Billing.&lt;/strong&gt; The other three count successful searches only. On RapidAPI every request that reaches my listing counts, one I reject as invalid included.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  APIs I couldn't run
&lt;/h2&gt;

&lt;p&gt;FlightAPI.io and Duffel only offer password sign-ups (I only used Google sign-ins for this), Duffel is a booking API with test data anyway, Amadeus Self-Service closed in July 2026, and Kiwi Tequila, Skyscanner and Travelpayouts need an application, an invitation or a traffic minimum. Sources for each are on the &lt;a href="https://flightpowers.com/guides/flight-api-benchmark-2026" rel="noopener noreferrer"&gt;benchmark page&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;If you've used any of these in production, I'd like to know which number actually made you pick one. The full table, the method and the per-call JSON are on the page :)&lt;/p&gt;

</description>
      <category>api</category>
      <category>webdev</category>
      <category>benchmark</category>
      <category>travel</category>
    </item>
  </channel>
</rss>
