...
| Parameter | Values | Description / Comments | For example |
|---|---|---|---|
| airport | Required max: 3-4 characters value, ex. OSL, BGO, TOS | The operating airport that considers the flight leg orientations. Formatting is given as IATA airport code and must written in uppercase letters. Parameter is required! | airport=OSL, airport=BGO, etc. |
| TimeFrom | Optional defaults to value: 1 if not set Max value: 96 | The number of hours before the current time for which data is wanted. | TimeFrom=1 |
| TimeTo | Optional defaults to value: 7 if not set Max value: 144 | The number of hours after the current time for which data is wanted. | TimeTo=7 |
| direction | Optional Accepted: A or D If not set: both flight-directions | If the parameter direction is set, then the Flights will be filtered by A=Arrivals or D=Departures. If parameter direction is not set then fetch all flight leg data for both orientations. | direction=A or direction=D |
| lastUpdate | Optional Accepted format: yyyy-MM-ddTHH:mm:ssZ ex: 2023-01-20T13:02:37Z | If set, then Flights that are updated after the given timestamp within the period of TimeFrom and TimeTo. Datetime has to be given in UTC/Z zone. Recommended for polling-applications looking for new updates to flights. | lastUpdate=2023-01-03T09:30:00Z |
| codeshare | Optional Accepted: Y | If set then codeshareinfo is added to flight. CodeshareInfo consists of codeshareAirlineDesignators, codeshareAirlineNames, codeshareFlightNumbers and codeshareOperationalSuffixs. | codeshare=Y |
| serviceType | Optional Accepted: E | Possibility to add helicopter flights with servicetype (“E”) parameter. If parameter omitted, schedule flights with servicetype ‘J’ (Schedule passenger) and ‘C’ (Charter passenger) are sent | serviceType=E |
Please note that if incorrect syntax is used on a parameter, that parameter will be left out and its default values will be used.
Example where all there parameters are used:
Prod:
...
Other useful links:
XML schema file.
The XML schema files for the LETIS based service is obtained from the URL:
...
Example: 2009-12-31T16:00:00 corresponds to 31. Descember 2009 17:00 o'clock local time in Norway (CET), while 2009-06-23T16:00:00 correcsponds to 23. June 2009 18:00 o'clock local time in Norway (Summertime).