Authenticate with the OAG Developer Portal to obtain your API key; review the Flight Info Alerts product tier for your required coverage (global vs regional) and update frequency.
Configure an alert subscription via the OAG API specifying the filter criteria: carrier code, departure airport, or specific flight number range; set the delivery method to HTTP push (webhook) or configure the event hub endpoint.
Implement the receiving webhook: OAG pushes JSON events containing flight_id, event_type (e.g., DELAY, CANCELLATION, GATE_CHANGE), the affected departure/arrival times, and the new values.
On receipt of a CANCELLATION or significant DELAY event (threshold configurable), look up affected bookings in your system by matching the carrier + flight_number + departure_date composite key.
Trigger downstream passenger notifications and, where applicable, initiate the IROPS or refund workflow based on the event type and delay magnitude.
Reconcile the OAG event timestamps against the booking departure times using UTC — OAG reports all times in UTC with a utc_offset field for local time reconstruction.
Known gotchas
OAG Flight Info Alerts does not guarantee zero message loss — implement an idempotent event handler keyed on the OAG event_id to avoid duplicate processing of retried deliveries.
Gate change events are frequent and mostly non-actionable for remote booking systems; filter aggressively to avoid alert fatigue — focus on status events crossing your defined delay thresholds.
OAG flight coverage exceeds 97% of worldwide flights, but status data for some regional carriers and smaller airports may lag real-time by several minutes — do not use OAG as the sole source for compliance-sensitive delay calculations.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp