Google flights calendar search

Run job:search.google-flights-calendar through the looot API: 1 provider, from $0.004 per call. Inputs, prices, output shape and code for curl, JavaScript and Python.

Google flights calendar search.

Job id search.google-flights-calendar, in Search & SERP (Search engines). As of 2026-10-01, 1 provider serve it through 1 tool. Run job:search.google-flights-calendar and looot picks one of them; with fallback on, a miss moves on to the next. See Jobs.

Inputs

This job has one tool, so it takes that tool’s fields. Any key you send passes through unchanged.

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

Providers and prices

Provider	Tool	Price
SearchAPI.io	`searchapi-io-google-flights-calendar`	$0.004 per call

A call that fails at the provider costs $0. See What’s free.

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":"job:search.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: "job:search.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": "job:search.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 pin one provider, send its tool id as endpointId instead of job:search.google-flights-calendar.