Service facts

• Name: FlightDataRequestServiceExtended

• Operations: 

  • GetFlightLegDataExtended

• Service is accessed using HTTPS GET

• Service security: Decided by implementation

• Standard return codes are described here: HTTP Return Codes

Introduction

Overview

This service is an extended version of the Flight Data Request Service v 2.0. The services will be maintained in sync, and all core data returned by GetFlightLegDataExtended is identical to the  data returned by GetFlightLegData. In addition passenger and more detailed baggage data is returned.

Flight Data Request Service Extended v 2.0 is defined as a separate service to enable a simpler security model. Since passenger numbers per flight are considered business sensitive data it is important to restrict access to this service.

Please see Flight Data Request Service v 2.0 for a general description of the service.

Implementation considerations

Any implementation of this service MUST use the XSD files provided here: XSDs

It is however up to the service provider which data elements to support, and how much data to return for requests spanning a long time period. To enable this most elements are optional. The reason for a service provider to not support all elements might be business rules related to data distribution, that it doesn't have the information, or that it wants to provide information in other (more restricted) ways.

Any service provider should make available documentation about the actual implementation, including:

• • the address of the service.
  • any limitations in the implementation.
  • recommended and allowed polling intervals.

Purpose of this service description

This service description has the following purpose:

• • • Describe of service in enough detail for a service provider to implement it.
    • Describe the service so that a client (of this service) developer can use it.
    • Make available the XSD files necessary to implement and use the service.
    • Make it possible for relevant people at airports, airlines, handlers and other aviation partners to understand the available functionality and then to decide if to implement/use it or not.

Intended readership

• • IT architects
  • Developers
  • Business architects
  • Interested parties in the aviation community

Service overview

Service operations

Data entities

XSDs