departure_idstringrequired
origin airport/location code
Google Flights Search
https://api.sandbase.ai/v1/api/google-flights/searchGoogle Flights itineraries for a route and date: airlines, times, stops, durations, prices and price insights.
- Price
- $0.01USD / call
- Method
- POST
- Response
- JSON
- Parameters
- 3 required · 3 optional
Playground
Input
origin airport/location code
destination airport/location code
YYYY-MM-DD
1 round trip (default) | 2 one way | 3 multi-city
YYYY-MM-DD, required when type=1
currency
OutputReady
Your output will appear here
Complete the inputs, then click Run.
API README
Google Flights Search API
Google Flights itineraries for a route and date: airlines, times, stops, durations, prices and price insights.
Request
curl -X POST "https://api.sandbase.ai/v1/api/google-flights/search" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"departure_id": "CDG", "arrival_id": "AUS", "outbound_date": "2026-12-15", "type": "2"}'
The result is returned in outputs[0].data.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
arrival_id | string | Yes | destination airport/location code |
departure_id | string | Yes | origin airport/location code |
outbound_date | string | Yes | YYYY-MM-DD |
currency | string | No | currency |
return_date | string | No | YYYY-MM-DD, required when type=1 |
type | string | No | 1 round trip (default) / 2 one way / 3 multi-city |
Pricing
Flat price per call. Failed calls are not charged.
Start building
Send your first request
Platform API endpoint with unified authentication and usage tracking.
# The quoted heredoc keeps Unicode and shell metacharacters unchanged.
result=$(curl --fail-with-body --silent \
-X POST "https://api.sandbase.ai/v1/api/google-flights/search" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
--data-binary @- <<'SANDBASE_JSON'
{
"type": "2",
"arrival_id": "AUS",
"departure_id": "CDG",
"outbound_date": "2026-12-15"
}
SANDBASE_JSON
)
printf '%s\n' "$result"2. Authentication
Set your SandBase API key in your server environment. Requests use Bearer authentication.
export SANDBASE_API_KEY="YOUR_API_KEY"Keep your key on the server. Do not expose it in browser code.
3. Parameters
arrival_idstringrequired
destination airport/location code
outbound_datestringrequired
YYYY-MM-DD
typestring
1 round trip (default) | 2 one way | 3 multi-city
return_datestring
YYYY-MM-DD, required when type=1
currencystring
currency
4. Response
Saved example response for this API; no live request is made when viewing it.
No saved response has been published. Run the API in Playground to inspect its response.
Explore more
Related APIs
| API | Price | Response |
|---|---|---|
Google Flights SearchThis API Google Flights | $0.01 per call | JSON |
Questions
FAQ
How do I use the Google Flights Search API?
Send a POST request to https://api.sandbase.ai/v1/api/google-flights/search with your SandBase API key in the Authorization header (Bearer) and the parameters as a JSON body. You can also try it in the Playground on this page without writing code.
How much does the Google Flights Search API cost?
$0.01 per call, billed from your SandBase balance. You are only charged for calls you make; there is no subscription.
What parameters does the Google Flights Search API accept?
Required: departure_id (string), arrival_id (string) and outbound_date (string). Optional: type (string), return_date (string) and currency (string). The Parameters table and the Playground on this page list every field.
What does the Google Flights Search API return?
A JSON response returned in the same HTTP request (synchronous).
Do I need a Google Flights developer account or API key?
No. Google Flights Search runs through SandBase, so one SandBase API key covers this endpoint and every other API and model in the catalog. You do not need to apply for Google Flights API access separately.