Discover/iFlyOAK API
live

iFlyOAK APIiflyoak.com

Get real-time arriving flight data for Oakland International Airport (OAK) including flight number, status, gate, terminal, and scheduled times.

This API takes change requests — .
Endpoint health
verified 2h ago
get_arriving_flights
1/1 passing latest checkself-healing
Endpoints
1
Updated
2h ago

What is the iFlyOAK API?

The iFlyOAK API exposes 1 endpoint — get_arriving_flights — that returns the full list of flights currently scheduled to arrive or recently arrived at Oakland International Airport (OAK). Each record includes 8 or more fields: origin city, airline name, flight number, scheduled and estimated arrival times in UTC, current status, terminal assignment, gate, and origin airport name, giving you a complete snapshot of OAK arrival activity.

Try it

No input parameters required.

api.parse.bot/scraper/5fd70959-e4c5-437d-b8df-836d40661a2a/<endpoint>
Ready to send
Fill in the parameters and hit sign in to send to see live response data here.
Call it over HTTPgrab a free API key at signup
curl -X GET 'https://api.parse.bot/scraper/5fd70959-e4c5-437d-b8df-836d40661a2a/get_arriving_flights' \
  -H 'X-API-Key: $PARSE_API_KEY'
Python SDK · recommended

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 iflyoak-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: Oakland Airport (OAK) flight arrivals — bounded, re-runnable."""
from parse_apis.iflyoak_com_api import OaklandAirport, ParseError

client = OaklandAirport()

# List all arriving flights, capped at 3 for demonstration
for flight in client.flights.list(limit=3):
    print(flight.airline, flight.flight_number, flight.arriving_from, flight.status)

# Get the first flight for detailed inspection
first = client.flights.list(limit=1).first()
try:
    print(first.scheduled, first.estimated, first.terminal, first.gate, first.origin_airport)
except ParseError as e:
    print(f"error: {e.code}")

print("exercised: flights.list")
All endpoints · 1 totalmissing one? ·

Returns all flights currently scheduled to arrive or recently arrived at Oakland International Airport (OAK). Each flight includes origin city, airline, flight number, scheduled and estimated times (UTC), current status, terminal, gate, and origin airport name. The list is refreshed by the airport periodically and represents the full current arrival board.

Input

No input parameters required.

Response
{
  "type": "object",
  "fields": {
    "total": "integer count of flights returned",
    "flights": "array of arriving flight objects"
  },
  "sample": {
    "total": 58,
    "flights": [
      {
        "gate": "14",
        "status": "Arrived / Gate Arrival",
        "airline": "Alaska",
        "terminal": "1",
        "estimated": "2026-07-15T23:41:20Z",
        "scheduled": "2026-07-15T23:57:00Z",
        "arriving_from": "Portland",
        "flight_number": "2035",
        "origin_airport": "Portland Intl"
      },
      {
        "gate": "-",
        "status": "En Route / On Time",
        "airline": "Volaris",
        "terminal": "1",
        "estimated": "2026-07-16T01:09:00Z",
        "scheduled": "2026-07-16T01:08:00Z",
        "arriving_from": "Guadalajara",
        "flight_number": "1770",
        "origin_airport": "Don Miguel Hidalgo y Costilla Int'l"
      }
    ]
  }
}

About the iFlyOAK API

What the API Returns

The single get_arriving_flights endpoint returns a JSON object with two top-level fields: total (an integer count of flights in the current list) and flights (an array of flight objects). Each flight object carries the airline name, flight number, origin city, origin airport name, scheduled arrival time, estimated arrival time, current status, terminal, and gate — all reflecting conditions at OAK as of the most recent data refresh.

Endpoint Details

get_arriving_flights takes no input parameters. Every call returns the full current arrivals board for Oakland International Airport. Times are expressed in UTC, so downstream consumers are responsible for any timezone conversion needed for display. The status field reflects real-time states such as on time, delayed, landed, or cancelled. The gate and terminal fields are included when the airport has assigned them.

Data Scope and Freshness

Coverage is limited to Oakland International Airport (OAK / IATA). The dataset does not include departures, SFO, or SJC flights. Because the endpoint reflects the live arrivals board, results change between calls as flights progress through their lifecycle — from scheduled through landed. There is no historical archive; only the current arrivals window is available.

Reliability & maintenanceVerified

The iFlyOAK API is a managed, monitored endpoint for iflyoak.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when iflyoak.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 iflyoak.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.

Last verified
2h ago
Latest check
1/1 endpoint passing
Maintenance
Monitored & self-healing
Will this API break when the source site changes?+
It's built not to. Every endpoint is health-checked on a schedule with automated test probes. When the source site changes and a check fails, the API is automatically queued for repair and re-verified — that's the self-healing layer. Each API page shows when its endpoints were last verified. And because marketplace APIs are shared, any fix reaches everyone using it.
Is this an official API from the source site?+
No — Parse APIs are independent, managed REST wrappers over publicly available data. That is the point: where a site has no official API (or only a limited one), Parse gives you a maintained, monitored endpoint for that data and keeps it working as the site changes — so you get a stable contract over a source that never promised one.
Can I fix or extend this API myself if I need a new endpoint or field?+
Yes — and you don't have to wait on us. This API was generated by the Parse agent, which stays attached. Describe the change in plain English ("add an endpoint that returns reviews", "fix the price field") in the revise box on the API page or via the revise_api MCP tool, and the agent rebuilds it against the live site in minutes. Contributing the change back to the public API is free.
What happens if I call an endpoint that has an issue?+
Errors are machine-readable: a bad call returns a clean status with the list of available endpoints and a repair hint, so an agent (or you) can recover or trigger a fix instead of failing silently. Confirmed failures feed the automatic repair queue.
Common use cases
  • Display a live OAK arrivals board on a travel or airport companion app using status, gate, and terminal fields.
  • Send delay alerts to passengers by comparing scheduled vs. estimated arrival times across polling intervals.
  • Track airline on-time performance at OAK by logging status values over time for each carrier.
  • Power a ground-transportation dispatch tool that triggers driver assignments when a flight status changes to 'landed'.
  • Build a kiosk or notification system that surfaces gate and terminal assignments for meeters and greeters.
  • Aggregate origin city and airline data to analyze which routes serve OAK most frequently.
Pricing & limitsSee full pricing →
TierPriceCredits/monthRate limit
Free$0/mo1005 req/min
Hobby$30/mo1,00020 req/min
Developer$100/mo5,000100 req/min

One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.

Frequently asked questions
Does iFlyOAK have an official developer API?+
iFlyOAK (iflyoak.com) does not publish an official developer API or documented data feed for flight status information.
What does the `get_arriving_flights` endpoint return for each flight?+
Each flight object includes the airline name, flight number, origin city, origin airport name, scheduled arrival time (UTC), estimated arrival time (UTC), current status, terminal, and gate. The total field at the top level gives the count of flights in that response.
Does the API cover departures from OAK, or flights at nearby airports like SFO or SJC?+
Not currently. The API covers only arriving flights at Oakland International Airport (OAK). Departures, SFO, and SJC are not included. You can fork it on Parse and revise to add those missing endpoints.
Can I filter results by airline, status, or terminal?+
The endpoint returns the full arrivals list without server-side filtering options. Filtering by airline, status, terminal, or gate needs to be done client-side on the returned flights array. You can fork the API on Parse and revise it to add filtered endpoints if you need that behavior built in.
How current is the arrivals data, and is historical flight data available?+
The endpoint reflects the live arrivals board at OAK and updates as conditions change. No historical archive is exposed — only the current arrivals window is returned. Each call gives a point-in-time snapshot; storing results over time to build history must be handled by the consuming application.
Page content last updated . Spec covers 1 endpoint from iflyoak.com.
Related APIs in TravelSee all →
flylax.com API
Access data from flylax.com.
flightradar24.com API
Track live flights worldwide, view real-time airport schedules, and search for specific flights with detailed information about aircraft and routes. Monitor the most tracked flights and get comprehensive airport details including gates, terminals, and operational status.
flysfo.com API
Access data from flysfo.com.
flightradar.com API
Track flights in real-time, search for specific flight details, and look up information about airports and airlines worldwide. Monitor nearby aircraft by location, identify which airlines operate specific routes, and get comprehensive aviation data all in one place.
justfly.com API
Search flights and get airport suggestions to find the best deals on JustFly.com, with instant access to flight details and trending destinations. Discover discounted airfare offers and compare flight options all in one place.
aa.com API
Search for real-time American Airlines flight information including departure/arrival times, gates, terminals, and aircraft details, plus look up airports and countries to plan your travel. Get live flight status updates and discover available amenities for your journey.
jfkairport.com API
Access data from jfkairport.com.
skiplagged.com API
Search for flights across airlines including hidden-city ticketing options, and look up airport information by name or code to find the best travel deals. Access Skiplagged's flight inventory and routing data to discover cheaper itineraries and alternative airport combinations.