Travelfusion Direct Connect XML API >

Incremental Updates

This service enables the customer to poll for all new/ up-to-date flight prices that Travelfusion obtains from any source, as soon as it is obtained.

To receive this data:

Poll repeatedly until no data is returned.
Stop polling for 1 minute.
Go back to step 1.

Polling

The polling request looks like this:

</GetIncrementalUpdates>

</CommandList>

The value of 'LastPoll' should be whatever you received in our previous response querying for the same supplier in the 'LastPoll' element (use 0 in case of no previous requests), i.e. you will have to track 'LastPoll' value per supplier.

You must submit CompressedSegments with value 'true'. As a result the 'SegmentList' element (see below) will be omitted and a compressed version will be returned instead. The format is described here: Compressed Segments.

The response looks like this:

<Fares>

<Supplier>ryanair</Supplier>

<Type>airport</Type>

</Origin>

<Type>airport</Type>

</Destination>

<TravellerType>adult</TravellerType>

<DoNotUseForOneways>false</DoNotUseForOneways>

<DoNotUseForRoundtrips>false</DoNotUseForRoundtrips>

<Group>

</CacheInfo>

<Price>

<Name>Taxes and Fees</Name>

</TaxItem>

</TaxItemList>

</Price>

<Type>airport</Type>

</Origin>

<Type>airport</Type>

</Destination>

<Name>Ryanair</Name>

</TFOperator>

<Name>Ryanair</Name>

</TFVendingOperator>

<Name>Ryanair</Name>

</Operator>

<Name>Ryanair</Name>

</VendingOperator>

</FlightId>

<SupplierClass>Economy With Restrictions</SupplierClass>

</TravelClass>

<SegmentMayEndWithAStop>false</SegmentMayEndWithAStop>

</Segment>

</SegmentList>

</Outward>

</OutwardList>

</Group>

</GroupList>

</Fares>

...........

</FaresList>

</GetIncrementalUpdates>

</CommandList>

Polling for grouped supplier could yield different response, 'Price' element could appear at 'Group' level, leg prices might not be present, example(with compressed segments mentioned below enabled):

<Group>

<Price>

...........

</TaxItemList>

</Price>

</CacheInfo>

...........

</CompressedSegmentList>

</Outward>

</OutwardList>

</CacheInfo>

...........

</CompressedSegmentList>

</Return>

</ReturnList>

</Group>

Please refer to CheckRouting Response for detailed descriptions of generic xml elements, specifically group and leg level 'Price' description, to be able to determine roundtrip price correctly for grouped suppliers.

Note

For some grouped suppliers outward and return leg's segments' departure date might not match

FaresList>Fares>OutwardDate/ReturnDate. Please use Segment's departure date in such cases to determine actual outward/return dates.

Note

Passenger breakdown is not provided within 'Price' element at the moment as prices are per one adult.

The following 3 elements have special meanings:

<DoNotUseForOneways>: If true, this indicates that the price is only valid as part of a roundtrip flight.

<DoNotUseForRoundtrips>: If true, this indicates that the price is only valid as a oneway flight.

<IsReturnPartOfRoundtrip>: If true, then this data was received as the return part of a roundtrip search.

This means that if you use this data for an outward flight, there is a risk that

the price will not be fully accurate due to currency conversion issues.

When this flag is false, the flight was an outward leg, and so there is a similar

risk in using the data as the return part of a roundtrip.

Travelfusion has now released a more concise version of this specification, as it currently creates a large amount of

unnecessary XML data (EDIT: see CompressedSegments added in the request above)

All customers are now required to move to the new format within a reasonable amount of time (3 months).