Skip to main content

Bridge Labs API Release Notes

Bridge Labs API Release Notes

February 2020

Historical Search

The Historical Data Search feature is back in service for the following APIs: 

  • Total Price Calendar Search
  • Fare Rule Merge with YQ/YR 


Routehappy Rich Content APIs

The Routehappy Rich Content APIs (Amenities, UPA/UTAs) have been added to the Bridge Labs program.

UPA & UTA API 
UPAs, Universal Product Attributes, are rich content that showcase and bring unique airline products and services to life. UPAs are targeted by aircraft, cabin, route, time of day, fare, and more, giving travelers relevant and useful merchandising content while they shop. 

UPAs include these content types:

  • Photos
  • Graphics
  • Videos
  • 360-degree tours
  • Descriptions
  • Captions


UTAs, Universal Ticket Attributes, are standardized, easy-to-integrate fare benefits and restrictions:

  • Brand names
  • Fare families (brand codes)
  • Industry and carrier defined sub codes
  • Standardized headlines and descriptions
  • Assessment metadata for comparison grids
  • Penalties and fees


Amenities API
Amenities provide consumers precise, targeted information about the onboard experience at a glance with content in the following categories:

  • Seat
  • Aircraft
  • Layout
  • Wi-Fi
  • Entertainment
  • Power
  • Food
  • Beverages


If you are interested in historical data search, please contact Bridge Labs at labs@atpco.net.

 

January 2020

Fare Rule Merge with Metadata API

  • Category 31 (Voluntary Changes) has been added to this API and is now enabled by default. 


You may now request preferred categories by sending comma-separated categories in request.

Sample:



  • Bug fixes

December 2019

Total Price Calendar Search API

  1. New request parameter 'itineraryDetail', value of boolean with default of 'true' is added in this API, which returns the Itinerary Details in the response. A value of false will suppress the itinerary details from being returned.
    1. /pricing/search
    2. /pricing/od


Sample Usage#
https://developer.atpco.net/services/v1/totalprice/pricing/search

{
"tripType": "RT",
"route" : ["ORY-RUN"],
"carriers": [
    "AF"
],
"ticketDate": "2019-09-10",
"asOfDateTime": "2019-09-10",
"travelStartDate": "2019-09-10",
"travelEndDate": "2019-10-10",
"itineraryDetail":false
}

 

Fare Rule Merge with Metadata API

  1. All categories now show an infinity symbol (∞) for discontinue dates. Previously they were shown as '3000-01-01'. This change will make sure that all end dates are in sync.
  2. All the categories will follow the same order in the response. Previously, the order was random.
  3. Category 14 (Travel Restrictions) was modified to identify a fare with no valid travel dates.
  4. Category 33 (Voluntary Refunds) was modified to show discounts in the response (if available).


Other changes

  • Historical database to query data dated before 24 November 2019 will NOT be available for the next few days during a maintenance period. We will inform all the Bridge Labs participants when it is available again.

October 2019

Fare Rule Merge with Metadata API

  • Added Category 33 (Voluntary Refunds) implementation, which is enabled by default. Otherwise you may send a comma-separated list of the categories you want to receive in the request.

    Here is a sample of Category 33 data:

    bridge labs api release notes

  • Fixed bug involving consolidation of fare rules and general rules.

September 2019

Fare Rule Merge with Metadata API

  • Added a new parameter: “detail” with values “true” or “false”. 
    The default value is “false”. When it is turned to “true”, the response will include the Footnotes and Rules sequence keys that were used to create the application restrictions. ATPCO subscribers can use those keys to look up application records from the Footnotes and Rules subscription files. 

  • Added a new parameter “geoSpec” with value “true” or “false”. 
    When the value is “true”, it will return the GeoSpec coding information, where applicable, for certain categories in metadata. A potential use for this GeoSpec coding information would be used to validate whether the restriction applies for a specific itinerary. For example, if the information is “Min Stay -> If (Location=WAS) 7 days”, the minimum stay only applies if the itinerary was via WAS. 

  • Bug fixes and performance improvements: Fixed the issue with duplicated fares in the API response.

  • Requested your feedback
    What “rich” information would you like to receive in the API response?

    • Branded data associated to the fare
      Such as the name of the brand and the ancillary services that accompany the fare

    • Dual RBD
      The Fare Class has the prime RBD, but if an airline is using Dual RBD for upselling and/or upgrade, there is a second RBD needed (held in ATPCO Rules data Table 999). If you didn’t receive the second RBD, there could be two or more fares in the same prime RBD that look the same and that you couldn’t differentiate. Currently our API response only includes the prime RBD.