UTAs

The Routehappy API endpoint provides access to UTAs (as well as UPAs and Amenities). UTAs (Universal Ticket Attributes) are benefits and restrictions by fare, in plain, simple language that make it easy for travel agents and customers to understand. UTAs are sourced from airline ATPCO fare, branded fare and optional service filings and then processed into clear and concise merchandising content.

UTA Data Types

All UTA data types are sourced from ATPCO rules data. Filed data is reflected in the final response structure for each type (e.g., in the assessment, fee, headline, and description fields).

Headline/Description templates and assessments are sourced from the UTA DataKit.

* The System Assumption for Changes and Refunds dictates that the respective policy's conditions are permitted free of charge with no restrictions.

Example Headline/Description Pairs

Below are the possible Headlines and Descriptions that you receive for each UTA category.

Advance Change

Back to the table

Cancellation

Back to the table

Checked Baggage

Back to the table

Carry-on Baggage

Back to the table

Boarding Priority

Back to the table

Check-in Priority

Back to the table

Lounge Access

Back to the table

Same-day Change

Back to the table

Seat Selection

Back to the table

Upgrade Eligibility

Back to the table

Loyalty Rewards

Back to the table

Requesting UTAs

You can specify a request for UTAs using the includes parameter and filter the attributes in that response using the ticket_attributes_filter. You can also set os_override to request using data from branded fares for advance change, baggage, and cancellation, instead of baggage engine.

{
  "control": {
    "includes": [
      "uta"
    ],
    "ticket_attributes_filter": [        // include the attributes
      "advance_change",                  // you'd like in the response
      "boarding_priority",
      "brand",
      "cancellation",
      "carry_on_baggage",
      "checked_baggage",
      "check_in_priority",
      "lounge_access",
      "upgrade_eligibility",
      "loyalty_rewards"
    ],
    // ...
  },
  // ...
}

Data Hierarchy

Advance change and Cancellation data in both the Routehappy API and Hub Backwards Compatible endpoints is sourced from Fare Rules. Fare Rules provides the most granular form of the data, which will be returned as a “policy” (e.g. “change_policy” or “cancel_policy”).

Carry-on baggage allowance and Checked baggage allowance data in both the Routehappy API and Hub Backwards Compatible endpoints are sourced from Optional Services.

For the remaining 6 categories, Same-day change, Seat selection, Check-in priority, Boarding priority, Upgrade eligibility, Lounge access, data will be sourced from Branded Fares for airlines who file these categories. Airlines are not required to file data across all categories, so coverage will vary by category by airline. For a full breakdown of UTA coverage by category and airline, please see our Coverage page. Additionally, Airlines can restrict who they share their data with by electing to only share with Channels using certain fare sources. For instance, an airline may choose to only share data if a Channel’s indicated fare source is Sabre rather than Amadeus or Worldspan. If the Coverage page shows that data are available for an airline, but you are unable to access data for that Airline, please submit a support ticket so we can help you resolve the issue.

UTA Data Accuracy

UTAs return the most currently available data the airlines have provided to ATPCO. Any change an airline makes to their ATPCO fare filings should be reflected in UTA data within an hour of being updated.

Icons

Icons are generic and included in each UTA as a pointer URL. Partner can choose whether or not to utilize them for display.

Language Translation

The Routehappy UTA API display text is available for the following languages/regions.

Units of Measurement

Measurement is dictated by the language/localization indicated. For the U.S. English, all measurements follow the United States customary system (USCS) for units of measurement. For all other languages/localizations, measurements are provided in metric units.