Our system is optimized for single flight segments. You must register individual flight alerts for each segment of the multi-segment flight.
First, look up the desired flight legs using the Schedules API:
Comment: If you do not know whether it is multi-segment, then you can search the schedules by route, with the "includeDirects" extended option, then look at the number of stops field. The individual segments would then be discovered by searching with one airport only, without includeDirects (thus non-stops only).
Then create individual flight rules for each flight leg using Flight Alert by Departure and Flight Alert by Arrival:
For multi-segment-flight A->B->C:
- Create a flight rule monitoring A->B by departure date.
- Create a second flight rule monitoring B->C by arrival date (please make sure to set the arrival date correctly if it crosses a date boundary).
If you are contracted for Multi-Segment Alerts, you'll have the ability to set up Multi-Flight Rules:
Multi-Flight Rules monitor a category of flights, regardless of how many flights that may be. Multi-Flight rules exist until deleted. They are created with these endpoints:
- By Arrival Airport: All flights arriving at a given airport (e.g. all arrivals at LHR)
- By Departure Airport: All flights departing at a given airport (e.g. all departures from LHR)
- By Primary Marketing/Operating Carrier: All flights where the carrier is the primary marketer or operator (e.g. all DL flights)