The API Report CardAPI Index
OAG

OAG API

Fleet / Trucking / Logistics · oag.com

OAG's Flight Info REST APIs are self-serve at developers.oag.com: schedules, status, connections, and push alerts, fronted by Azure API Management with subscription-key auth. The free trial is 14 days and 100 hits; paid tiers and enterprise data feeds are priced after signup or through sales.

Last verified: July 2026Hospitality & Travel
API GRADE
A
VERIFIED JUL 2026

SCORECARD

ExistenceGOODREST Flight Info APIs cover schedules for 900+ airlines, real-time status, seat capacity, connections, and push alerts.
AccessGOODSelf-serve signup with a 14-day, 100-hit free trial; tier pricing and overage rates appear only after signup.
CoverageGOODSchedules up to 24 months forward, operational status, seat capacity, 200M+ connections, and reference data are queryable.
AuthGOODA single Azure APIM subscription key per subscription, sent as a header; OAG warns to keep it server-side only.
Docs & DXGOODInteractive OpenAPI docs with a Try-It-Now sandbox and a knowledge base; no first-party SDKs, so teams hand-roll clients.
StabilityGOOD
Supergood: OAG shipped a real API. Most vendors don't; we ship near-native APIs for the rest.

Frequently asked questions

OAG scores A on the API Report Card. OAG's Flight Info REST APIs are self-serve at developers.oag.com: schedules, status, connections, and push alerts, fronted by Azure API Management with subscription-key auth. The free trial is 14 days and 100 hits; paid tiers and enterprise data feeds are priced after signup or through sales.

Tried to integrate with OAG?
SOURCES
Azure APIM subscription-key auth (header-based but a single shared secret per subscription) leaks into nginx, CloudFront, Datadog and any logging layer that captures full headers - mishandled keys are a recurring enterprise-integration concern developers.oag.com
OAG explicitly tells developers not to enable CORS / not to call the API from the browser because the subscription key would leak - this forces every integrator to stand up a server-side proxy even for trivial dashboards developers.oag.com
14-day, 100-hit free trial is too small to evaluate a production workload (typical OTA / corporate-travel polling on a single itinerary can exceed 100 hits in a day), pushing teams into a paid tier or sales motion before integration is validated travelpayouts.com
Pricing is fixed-fee per tier plus per-hit overage with the actual tier table not publicly listed - cost forecasting requires sign-up and per-tenant negotiation knowledge.oag.com
No published Enterprise rate limits; throttling semantics (429 responses, Retry-After headers, burst vs. sustained allowances) are documented inconsistently developers.oag.com
No first-party SDKs - integrators hand-roll HTTP clients and maintain their own retry/backoff/deduplication logic developers.oag.com
Push-based Flight Info Alerts has limited public documentation around webhook retry policy, replay tooling and idempotency guarantees - silent drops during receiver outages are a common parametric-insurance complaint pattern across this category oag.com
Two portal experience: developers.oag.com for the self-serve REST family vs. oag.com for the enterprise Snowflake/bulk/airfare products - integrators that start in one path often discover they need the other mid-build developers.oag.com
Knowledge base (knowledge.oag.com) is split from the developer docs (developers.oag.com) - common onboarding questions live in a different domain from the API reference knowledge.oag.com
Content parity gaps between the self-serve REST API and the enterprise Snowflake/bulk feeds - e.g. richer historical archive, airfare/Infare data, and certain master-data dimensions are enterprise-only and not exposed on the REST surface oag.com
Status-data update model is event-driven (operational events from airlines/airports), not continuous positional - integrators expecting ADS-B-style continuous tracking are surprised by the cadence vs. FlightAware/Flightradar24 altexsoft.com
Schedule data is canonical and refreshed every 15 minutes but the moment of canonical truth still depends on upstream airline ASM/SSM submissions - integrators occasionally see stale or mis-stated schedule entries that originate at the carrier altexsoft.com
Onboarding involves a three-step signup flow on the developer portal before keys are issued, slower than the 'instant key in browser' experience at AviationStack / FlightAPI.io travelpayouts.com
Health endpoints (/flights/health, /schedules/health, /master-data/health) exist but there is no public status page comparable to status.stripe.com - integrators have to poll health themselves to detect partial outages developers.oag.com
Premium pricing model - OAG is positioned as a premium enterprise data provider with fee structures per request subject to individual pricing and quota; difficult fee structures vs. transparent-priced competitors altexsoft.com
Event-based rather than positional tracking - lower tracking frequency vs. ADS-B-native providers (FlightAware, Flightradar24, ADS-B Exchange) - OAG status is updated on operational events not continuous position altexsoft.com
Two-portal experience: marketing/sales-led oag.com for enterprise contracts (Snowflake, bulk, airfare/Infare data) vs. self-serve developers.oag.com for the REST Flight Info family - integrators have to know which one to enter through developers.oag.com
Sales-gated enterprise pricing with no public rate card - the Snowflake share / bulk feed / Infare airfare / historical OTP archive products require a sales motion; engineers can't prototype against the full surface area travelpayouts.com
14-day free trial capped at 100 API hits is too small to do meaningful evaluation of a production workload, forcing teams into a paid tier or sales conversation before they can validate the integration travelpayouts.com
Brand and product ownership churn over decades (Dun & Bradstreet 1962 -> Maxwell Communications 1988 -> Reed Elsevier -> Electra Private Equity 2001 -> United Business Media 2006 -> Vitruvian Partners 2017) makes long-tail contract and IP provenance complex en.wikipedia.org
FlightView (acquired 2014) and Infare (acquired 2023) integrations are still being normalized into the unified OAG data surface, so airfare and real-time-tracking parity across products can lag oag.com
Documentation knowledge base lives on knowledge.oag.com separately from developer docs at developers.oag.com - integrators have to context-switch between portals to answer onboarding questions knowledge.oag.com
Snowflake-share delivery model requires customers to operate a Snowflake account (cost, governance, vendor lock-in) just to consume bulk schedule/airfare data oag.com
Customer-side data validation: OAG runs 350+ internal validation checks, but residual upstream airline submission errors still propagate; integrators have to defensively re-validate altexsoft.com
Slow product / pricing churn around the legacy FlightView consumer-tracking brand has confused customers about which product is canonical for live status altexsoft.com