Skip to content
looot docs
Esc
↑↓navigate↵open⌘Jpreview
On this page

SearchAPI.io - Google Flights Calendar API

SearchAPI.io tool searchapi-io-google-flights-calendar on looot: input fields, $0.004 per call, output shape, and code to run it with curl, JavaScript or Python.

The Google Flights Calendar API provides a comprehensive calendar view of flight prices across different dates, helping you find the most affordable travel dates for your trip. This API returns a calendar grid showing flight prices for various date combinations within a specified date range. For round-trip searches, it shows prices for different outbound and return date combinations. For one-way searches, it shows prices for different outbound dates only. Cross-linking: The departure_id and arrival_id parameters accept airport codes (e.g., “JFK”, “LAX”) or city codes (e.g., “/m/02_286” for New York). These IDs can be discovered using the Google Flights Location Search API.

Inputs

Name Type Required Description
adults integer no
arrival_id string yes
carry_on_bags integer no
checked_bags integer no
children integer no
currency string no
departure_id string yes
emissions string no
engine string no Fixed to “google_flights_calendar” for this endpoint. Example: “google_flights_calendar”
excluded_airlines string no
excluded_connecting_airports string no
flight_type string no
gl string no
hl string no
included_airlines string no
included_connecting_airports string no
infants_in_seat integer no
infants_on_lap integer no
layover_duration_max integer no
layover_duration_min integer no
max_flight_duration integer no
max_price integer no
outbound_date string yes
outbound_date_end string no
outbound_date_start string no
outbound_times string no
return_date string no
return_date_end string no
return_date_start string no
return_times string no
separate_tickets string no
stops string no
travel_class string no

Output

The run’s result holds the provider’s answer. Signed in, looot inspect searchapi-io-google-flights-calendar prints its fields.

Run it

Every call needs your API token in LOOOT_TOKEN; Sign in shows how to get one. Each run also needs a new idempotency key, so a retry never pays twice. With wait: 30 the answer comes back inline when the run ends within 30 seconds. Otherwise you get the running run back: poll GET /v1/runs/<runId>.

Example input with placeholder values:

curl -X POST "https://api.looot.ai/v1/runs" \
  -H "Authorization: Bearer $LOOOT_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{"endpointId":"searchapi-io-google-flights-calendar","input":{"departure_id":"<departure_id>","arrival_id":"<arrival_id>","outbound_date":"<outbound_date>","engine":"google_flights_calendar"},"wait":30}'
const response = await fetch("https://api.looot.ai/v1/runs", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.LOOOT_TOKEN}`,
    "Content-Type": "application/json",
    "Idempotency-Key": crypto.randomUUID(),
  },
  body: JSON.stringify({
    endpointId: "searchapi-io-google-flights-calendar",
    input: {
      departure_id: "<departure_id>",
      arrival_id: "<arrival_id>",
      outbound_date: "<outbound_date>",
      engine: "google_flights_calendar",
    },
    wait: 30,
  }),
});
const run = await response.json();
console.log(run.status, run.result);
import os
import uuid

import requests

response = requests.post(
    "https://api.looot.ai/v1/runs",
    headers={
        "Authorization": f"Bearer {os.environ['LOOOT_TOKEN']}",
        "Idempotency-Key": str(uuid.uuid4()),
    },
    json={
        "endpointId": "searchapi-io-google-flights-calendar",
        "input": {
            "departure_id": "<departure_id>",
            "arrival_id": "<arrival_id>",
            "outbound_date": "<outbound_date>",
            "engine": "google_flights_calendar",
        },
        "wait": 30,
    },
    timeout=90,
)
run = response.json()
print(run["status"], run.get("result"))

To let looot pick among every provider of this job instead, send job:search.google-flights-calendar as endpointId; see the job page.

Was this page helpful?