Flights Data Structure

API Structure

The structure of the API specification follows a standard. This document intends to explain every aspect of this structure and their fields.

The integration will have the following methods:

Element Input Output Required Description
Availability AvailabilityRQ AvailabilityRS Yes Return all the available options for a given date and itinerary. It does not filter different classes, times or fares. It will always return all of the results returned by the provider.
Valuation ValuationRQ ValuationRS Yes Return the total price of the selected Option, plus the extra supplements (price and information required in ReservationRQ) available in the Option. This Option must be selected in the previous step (Availability).
Reservation ReservationRQ ReservationRS Yes Book one or more Itineraries.
Emit (Issuance) EmitRQ EmitRS Yes* Issue the tickets. *Some suppliers don’t require the Emit operation. The payment is already resolved at Reservation step.
Refund RefundRQ RefundRS No This method aims to return all the available options for a given date and itinerary. It does not filter different classes, times or fares. It will always return all of the results returned by the provider.
Cancellation CancellationRQ CancellationRS No Cancel a booking.
RetrieveReservation RetrieveReservationRQ RetrieveReservationRS No Retrieve a booking with its full details.
RetrieveReservationList RetrieveReservationListRQ RetrieveReservationListRS No Return a list of bookings for a given time period being that either booking date or the travelling date, among other filters available.
Supplements SupplementsRQ SupplementsRS No Search for supplements (seat, baggage, etc).
ReservationSupplements SupplementsReservationRQ SupplementsReservationRS No Add supplements (seats, baggage, etc) to a reservation done previously.

Each request sent to the service url requires a node called rqXML. Inside this node travels the current method’s Input object.

The data structure will always have common elements in all objects and the specific objects related to the operation. Therefore, all the RQ and RS presented in the previous table, will have the following common structures:

Common RQ Structure Description

Element Number Type Description
timeoutMillisencods 1 Integer Timeout in milliseconds that the client will be waiting for the response.
source 1 Information about source requesting the operation.
source/agencyCode 0..1 String Agency code that requests the operation.
source/languageCode 1 String Language code (ISO 3166-1 alpha-2) format lowercase.
filterAuditData 1 Enables or disables information returned in audit data.
filterAuditData/registerTransactions 1 Boolean Returns all the transactions (XMLs) exchanged with the provider.
optionsQuota 1 Integer Sets the maximum number of Options returned.
Configuration 1 Information about source requesting the operation.
@providerCode 1 String Provider (supplier) code of the connection.
Configuration/Credentials 0..1 Required credentials for the conection with this provider.
@user 1 String User for the connection.
@password 1 String Password for the connection.
@officeId 0..1 String .
@iataCode 0..1 String .
1 String Url generic connection.
0..1 String Url for login/identification connection.
0..1 String Url for Avail method.
0..1 String Url for Valuation method.
0..1 String Url for Reservation method.
0..1 Parameters for additional information.
1..n List of parameter.
@key 1 String Contains the keyword/Id to identify a parameter.
@value 1 String Contains the value of the parameter.
Configuration/Attributes 0..1 Specific configuration parameters to this connector.
1..n List of parameter.
@key 1 String Contains the keyword/Id to identify a parameter.
@value 1 String Contains the value of the parameter.
ClientConfiguration 1 Client’s configuration.
@agency 1 String Agency name.
@currencyCode 1 String Currency code.
@mark 0..1 String Mark.
@businessLine 0..1 String Business line.
@accessLevel 0..1 String Access level.
@mean 0..1 String Mean.
@accessType 0..1 Access Type Access type.

Common RS Structure Description

Element Number Type Description
auditData 0..1 Returns the provider transaction logs if filterAuditData/registerTransactions has been set to true.
auditData/processTimeMilliseconds 1 Integer Time spend in the operation.
auditData/timeStamp 1 Date Timestamp when the operation begins. Example: 2019-02-12T07:38:14.4137201+01:00
auditData/transactions 1 Contains the RQ and RS of the provider transaction.
auditData/transactions/RQ 1 String Provider’s request transaction.
auditData/transactions/RS 0..1 String Provider’s response transaction. In case of timeout/server communication failure with the provider, this field may not be returned.
auditData/transactions/timeStamp 1 Date Timestamp when the provider transaction begins. Example: 2019-02-12T07:38:14.4137201+01:00
operationImplemented 1 Boolean If true, the operation requested is implemented. Some suppliers does not have all the operations implemented. In that case, this filed will return false.
ResponseStatus 0..1 Contains information regarding the operation executed.
@direction 0..1 Direction type Direction of the journey about to checkin.
@tripType 0..1 Trip type Trip type
@status 1 Response Status type Response Status type
applicationErrors 0..n List of errors occurred during the operation execution.
applicationErrors/code 0..1 String Provider error code.
applicationErrors/description 0..1 String Error description.
applicationErrors/type 0..1 Error types API error type.
Warnings 0..1 Contains a list of warnings.
Warnings/Warning 1..n Warning occurred during the operation execution.
@code 0..1 Error types API Warning code.
Warnings/Warning/text 1 String Warning description.

Date format

The date format depends to the element where it is placed. Two formats can be returned in RS:

Timezone specified Format Example
Yes YYYY-MM-ddTHH:mm:ss.fffffff+kk:kk
2019-02-12T07:38:14.4137201+01:00 (UTC+1)
2019-02-12T09:59:17.6756432Z (UTC)
No YYYY-MM-ddTHH:mm:ss.fffffff 2019-04-15T18:25:00

Date fields in RQ must be filled with same format that has been received from previous operation (if applicable) in same elements. Ex: if in RS’s segment you receive YYYY-MM-dd, you must send same format in the segments from next request.

Field Explanation Mandatory
YYYY Year Yes
MM Month Yes
dd Day Yes
T Time separator Yes
HH 24-hour clock hour, with a leading 0 (e.g. 22) Yes
mm Minutes Yes
ss Seconds Yes
fffffff Represents the seven most significant digits of the seconds fraction; that is, it represents the ten millionths of a second in a date and time value. No
+kk:kk Represents the time zone information of a date and time value (e.g. +05:00) No

Enumerate values

All the possible enumerate values are explained here.