Errors

Flight Information returns errors using a standard error format in XML when the call is successful but something failed, such as a request for flight information from an unsupported airline.

When requests to Flight Information contain more than one flight, errors are only returned for those flights that failed. Results for any flight requests that succeed are returned normally.

If any flight requests fail, an error displays under the <Flight> element rather than flight information details, as shown here:

<GWS_FlightInformationRS>

   <Flights>

      <Flight…>

         <Error>"Error Code and message here"</Error>

      </Flight>

   </Flights>

   <Decode>...</Decode>

</GWS_FlightInformationRS>

If the transaction in general fails, e.g. the request is bad, then only a single error section is returned, as a sibling to the root element (no <Flight> elements exists), as follows:

<GWS_FlightInformationRS>

   <Error>"Error Code and message here"</Error>

</GWS_FlightInformationRS>

Errors follow the standard Web Services Library error schema, which is essentially as follows:

<Error

   source=”Flight Information Web Service”

   code=”{code, unique for “source”}” >

   free form message text

</Error>

The following table outlines the error codes currently supported in Flight Information.

Error Code

Description

1

Airline not supported.

2

Invalid request.

3

Invalid origin city.

4

Invalid destination city.

5

Flight not found.

6

General application error.

7

General system error.

8

Invalid date.

10

Schedule change in progress.

11

Host system unable to process.

12

Flight cancelled.

13

Flight does not operate due to weather, mechanical, or other conditions.

14

Flight does not operate on days requested.

15

Flight does not operate between requested cities.

16

Requested flight not active.

17

General SDD interface error.

18

Transaction not allowed.

19

Host message function not supported error.

-1

General and unknown errors applicable to a flight. Only seen for inline flight errors.

-2

General and unknown errors applicable to entire call, such as request fails schema validation.

772

General Application Error. Includes:

validateInput: No Flights in requested Nodelist (If top level tag Flights is missing)

Invalid Request. No Flight items were specified (If there are no items within Flight)

Invalid Destination field (if less than 2 chars)

Invalid Airline (if less than 2 char)

Invalid Origin field (if less than 2 char)

Invalid Flight Number field (if less than 1 char)

Invalid Date field. Format must be YYYY-MM-DD (If the date is not in the desired format)