Aircraft Type now available in the Travelfusion XML API
Line BreakAuthor: Flyball (27 Articles)
Flyball is the Travelfusion mascot and logo – he'll be keeping his eye out for good deals, new technology and travel options and will post the most up to date information on our product development and services, along with new technology and announcements about Travelfusion, our suppliers and clients.
We are pleased to announce the release of a new feature within our XML API.
The type of aircraft operated by the supplier will now be included in flight results whenever it is available.
Currently a flight segment is returned as follows:
<Segment>
<Origin>
<Type>airport</Type>
<Code>LGW</Code>
<Terminal>South</Terminal>
</Origin>
<Destination>
<Type>airport</Type>
<Code>MAD</Code>
</Destination>
<DepartDate>16/06/2010-16:50</DepartDate>
<ArriveDate>16/06/2010-20:15</ArriveDate>
<Duration>145</Duration>
<TfOperator>
<Name>Easyjet</Name>
<Code>U2</Code>
</TfOperator>
<TfVendingOperator>
<Name>Easyjet</Name>
<Code>U2</Code>
</TfVendingOperator>
<Operator>
<Name>Easyjet</Name>
<Code>U2</Code>
</Operator>
<VendingOperator>
<Name>Easyjet</Name>
<Code>U2</Code>
</VendingOperator>
<FlightId>
<Code>U25479</Code>
<Number>5479</Number>
</FlightId>
<TravelClass>
<TfClass>Economy With Restrictions</TfClass>
<SupplierClass>Y</SupplierClass>
</TravelClass>
<SegmentMayEndWithAStop>false</SegmentMayEndWithAStop>
</Segment>
After the changes go live, this result may include aircraft type information as follows:
<Segment>
<Origin>
<Type>airport</Type>
<Code>LTN</Code>
</Origin>
<Destination>
<Type>airport</Type>
<Code>MAD</Code>
</Destination>
<DepartDate>17/06/2010-17:50</DepartDate>
<ArriveDate>17/06/2010-21:20</ArriveDate>
<Duration>150</Duration>
<TfOperator>
<Name>Easyjet</Name>
<Code>U2</Code>
</TfOperator>
<TfVendingOperator>
<Name>Easyjet</Name>
<Code>U2</Code>
</TfVendingOperator>
<Operator>
<Name>Easyjet</Name>
<Code>U2</Code>
</Operator>
<VendingOperator>
<Name>Easyjet</Name>
<Code>U2</Code>
</VendingOperator>
<FlightId>
<Code>U22205</Code>
<Number>2205</Number>
</FlightId>
<TravelClass>
<TfClass>Economy With Restrictions</TfClass>
<SupplierClass>Y</SupplierClass>
</TravelClass>
<AircraftType>
<AircraftName>Airbus Industrie A319</AircraftName>
<AircraftCode>319</AircraftCode>
</AircraftType>
<SegmentMayEndWithAStop>false</SegmentMayEndWithAStop>
</Segment>
In any flight segment, the entire AircraftType element may be omitted, or the AircraftName may be supplied without the AircraftCode or the AircraftCode without the AircraftName.
This is scheduled to be released to production on Saturday 20th February. The functionality can be tested on our mirror system (mirrorapi.travelfusion.com) from today and the new XML schemas are available at http://mirroradmin.travelfusion.com/xmlspec/v2/detailedspec/schemas.php
An example search that will return this information is LGW airport to MAD airport, one-way, 24th June. AircraftType will be returned for many of the suppliers’ results, including Easyjet flights.
This change is fully backwards compatible with our specification, but if this will cause problems for your application, please contact us as soon as possible.
If you enjoyed this post, please consider to leave a comment or subscribe to the feed and get future articles delivered to your feed reader.
Line BreakAuthor: Flyball (27 Articles)
Flyball is the Travelfusion mascot and logo – he'll be keeping his eye out for good deals, new technology and travel options and will post the most up to date information on our product development and services, along with new technology and announcements about Travelfusion, our suppliers and clients.
