Parameters for the request operations
All parameters are optional except parameter airport.
NB! All the parameters and its values are case-sensitive.
The semantics of each parameter are described in the table below.
| 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 |
| PeriodFrom | Optional If not set, defaults to 1 month back | The date of operation from for which data is wanted. If PeriodFrom is omitted flights with date of operation on ‘periodto’ and before are included in the result. | PeriodFrom=2023-01-19Z |
| PeriodTo | Optional Accepts format: yyyy-MM-ddZ ex: 2023-03-21Z If not set, defaults to value: all future | The date of operation to for which data is wanted. If PeriodTo is omitted flights with date of operation on ‘periodfrom’ and after are included in the result. If both PeriodFrom and PeriodTo are omitted, then all flights are included in the result. | PeriodTo=2023-01-21Z |
| direction | Optional Accepts: A or D If not set, defaults to both flight-directions. | The flight leg orientation. Data can 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 |
| designator | Optional Accepts between 1 to 4 characters. If not sety, defaults to all designators. | Flight identifier consists of the parameters ‘designator’ and ‘number’. Parameter ’designator’ should contain the airline designator part of the flight identifier. Airline code can be given as 2-signs IATA or 3-signs ICAO code. Airline code is max 3 signs. | designator=SK |
| number | Optional Accepts number between 3 and 4 digits. | Parameter ’number’ should contain the flight number part of the flight identifier. Flight number is number between 3 and 4 digits. | number=236 |
Please note that if incorrect syntax is used on a parameter, that parameter will be left out and its default values will be used.
Examples where all the parameters are used in url:
Prod:
Alternatively use this link:
XML schema file.
The XML schema files for the LETIS based service is obtained from the URL:
Service Response Elements
| Service term | ADD term | Comment |
|---|---|---|
| airline.designator | OperatingAirlineIata (part of FlightId) | |
| flight.number | FlightNumber (part of FlightId) | Derived from flight_id |
| operational.suffix | OperationalSuffix (part of FlightId) | Derived from flight_id |
| date.of.operation | FlightDepartureDate | |
| departure.station | DepartureAirportIATA | |
| std | SOBT | STD - ‘Scheduled time of departure (off-block)’. Date and time when a flight is scheduled to depart from the departure stand. |
| variation.std | N/A | Derived: by FlightDepartureDate and SOBT |
| arrival.station | ArrivalAirportIATA | |
| sta | SIBT | |
| variation.sta | N/A | Derived: by FlightDepartureDate and SIBT |
| aircraft.configuration | AircraftConfigVersion | |
| aircraft.owner | OperatingAirlineIata | |
| aircraft.type | AircraftIATAType | |
| service.type | FlightServiceTypeIATA | |
| creation | N/A | Derived: Shall be SSM |
| cancelled | FlightLegStatus | |
| route | FlightRouteIATA |
Time specifications:
All times are listed in UTC format and are in the format ISO 8601 (Wikipedia: ISO 8601-format) [YYYY]-[MM]-[DD]T[hh]:[mm]:[ss]Z. Please make sure to adjust for time zone and summer time as required.
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).