Flysfo APIflysfo.com ↗
Get real-time SFO security checkpoint wait times and flight status data via two endpoints. Covers all terminals, TSA PreCheck lanes, arrivals, and departures.
What is the Flysfo API?
The flysfo.com API provides 2 endpoints covering live security checkpoint wait times and flight status at San Francisco International Airport. get_security_wait_times returns current general and TSA PreCheck lane wait times for every checkpoint across all SFO terminals, while get_flight_status delivers a rolling 16-hour window of arrival and departure records including scheduled, estimated, and actual times.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/2f83e82a-83e5-4989-b8cd-042ffdaee2e9/get_security_wait_times' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace flysfo-com-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Walkthrough: SFO Airport SDK — bounded, re-runnable; every call capped."""
from parse_apis.SFO_Airport_API import SFO, FlightType, ParseError
client = SFO()
# List current security checkpoint wait times.
for checkpoint in client.checkpoints.list(limit=3):
print(checkpoint.checkpoint, checkpoint.general_wait_time, checkpoint.tsa_precheck_wait_time)
# List current departures from SFO.
for flight in client.flights.list(flight_type=FlightType.DEPARTURES, limit=3):
print(flight.flight_number, flight.airline, flight.origin_destination, flight.status)
# Get one arrival for quick inspection.
arrival = client.flights.list(flight_type=FlightType.ARRIVALS, limit=1).first()
try:
print(arrival.flight_number, arrival.airline, arrival.scheduled_time, arrival.gate)
except ParseError as e:
print(f"error: {e.code}")
print("exercised: checkpoints.list, flights.list")
Returns current security checkpoint wait times for all SFO terminals. Each checkpoint reports general and TSA PreCheck lane wait times. Wait times are subject to change and reflect live conditions. All gates are accessible from any checkpoint; checkpoint letters reference closest gates (e.g. Checkpoint B for Gate B1).
No input parameters required.
{
"type": "object",
"fields": {
"checkpoints": "array of checkpoint wait time records"
},
"sample": {
"checkpoints": [
{
"checkpoint": "Checkpoint A",
"general_wait_time": "1 mins",
"tsa_precheck_wait_time": "1 mins"
},
{
"checkpoint": "Checkpoint B",
"general_wait_time": "11 mins",
"tsa_precheck_wait_time": "7 mins"
},
{
"checkpoint": "Checkpoint B - Mezzanine Level",
"general_wait_time": "Not Available",
"tsa_precheck_wait_time": "4 mins"
},
{
"checkpoint": "Checkpoint D",
"general_wait_time": "1 mins",
"tsa_precheck_wait_time": "1 mins"
},
{
"checkpoint": "Checkpoint F",
"general_wait_time": "1 mins",
"tsa_precheck_wait_time": "1 mins"
},
{
"checkpoint": "Checkpoint G",
"general_wait_time": "1 mins",
"tsa_precheck_wait_time": "1 mins"
}
]
}
}About the Flysfo API
Security Checkpoint Wait Times
get_security_wait_times takes no inputs and returns a checkpoints array where each record covers a named SFO checkpoint. Each entry reports separate wait times for the general lane and the TSA PreCheck lane. The data reflects live conditions, so values can shift minute to minute. The checkpoint letter in each record indicates the closest gate cluster, though all gates remain accessible from any checkpoint.
Flight Status
get_flight_status accepts an optional flight_type parameter to filter results to either arrivals or departures. Without a filter, both directions are returned. Each record in the flights array includes the airline name, flight number, origin or destination city, terminal assignment, and scheduled, estimated, and actual times. The last_update field on the response indicates when the airport system last refreshed the data. The time window covers 12 hours ahead and 4 hours behind the current Pacific Time, giving a 16-hour view.
Coverage and Freshness
Both endpoints reflect SFO-specific data only. Wait times and flight records are sourced from the airport's live systems, so there is no historical archive and no coverage of other Bay Area airports (OAK, SJC). The last_update timestamp on flight responses lets callers detect stale data before acting on it.
The Flysfo API is a managed, monitored endpoint for flysfo.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when flysfo.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official flysfo.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Display TSA PreCheck vs. general lane wait times on a travel app to help passengers pick the fastest checkpoint
- Alert travelers via SMS when SFO security wait times exceed a configurable threshold
- Show gate-adjacent checkpoint recommendations based on terminal and checkpoint letter fields
- Build a real-time SFO arrivals board filtered by
flight_type: arrivalsfor an airport pickup service - Track departure delays by comparing scheduled vs. estimated times across flights
- Feed flight status records into a notification system for connecting passengers monitoring SFO layovers
- Aggregate TSA wait time history by polling
get_security_wait_timeson an interval for trend analysis
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does SFO publish an official developer API?+
What does `get_flight_status` return, and how does the `flight_type` filter work?+
get_flight_status returns a flights array of records within a 16-hour window (12 hours ahead, 4 hours past, Pacific Time). Each record includes airline, flight number, origin or destination city, terminal, and scheduled, estimated, and actual times. Passing flight_type: arrivals limits results to inbound flights; flight_type: departures limits to outbound. Omitting the parameter returns both directions. The last_update field shows when the underlying airport system last pushed a data refresh.How current are the security wait times?+
get_security_wait_times endpoint reflects live conditions reported by SFO's operational systems. Wait times can change between requests, and there is no last_update field on that endpoint — treat each response as a point-in-time snapshot. Polling on a short interval (e.g., every 60–120 seconds) is the standard pattern for near-real-time monitoring.Does the API cover historical wait times or flight history?+
get_flight_status. You can fork this API on Parse and revise it to add a persistence layer that stores polled responses over time.