Overview
The Aero API does not currently expose public endpoints for managing flight alerts. Alert functionality is handled internally by the system and is not documented in the public API specification.Future availability
Flight alert endpoints may be added in a future version of the API. These would potentially include:- Creating flight status alerts
- Managing alert subscriptions
- Configuring notification preferences
- Webhook endpoints for real-time notifications
Alternative solutions
While dedicated alert endpoints are not available, you can implement similar functionality using the existing API endpoints:Polling for flight status changes
Tracking flight position changes
Monitoring tracked flights
Best practices for polling
If you implement your own alert system using polling:- Respect rate limits: Don’t poll too frequently to avoid hitting API rate limits
- Use forceUpdate wisely: Only use
forceUpdate=truewhen you need the latest data - Implement exponential backoff: If you receive errors, increase the time between requests
- Cache results: Store previous responses to detect changes
- Filter important changes: Only notify users of significant status changes
Status changes to monitor
When implementing flight alerts, consider monitoring these key status changes:- Status changes:
scheduled→active→landed - Delays: Changes in
departureDelayorarrivalDelay - Gate changes: Updates to
gateOriginorgateDestination - Terminal changes: Updates to
terminalOriginorterminalDestination - Time updates: Changes to
estimatedOut,estimatedOff,estimatedOn,estimatedIn - Cancellations:
cancelledfield becomestrue - Diversions:
divertedfield becomestrue