Fare Rules Guide

Fare rules are the conditions and restrictions that apply to any reservation based on its fare type.

Related Content: Air Pricing Guide, Fare Rules API Reference

In this topic:

Basic Concepts

Fare rules determine the price of the fare. Generally, less expensive fares have more restrictions and more expensive fares have fewer restrictions. Fare rules can include blackout dates, advanced reservation requirements, minimum and maximum stay requirements, and cancellation and change penalties.

The JSON APIs return fare rules as distributed through their ATPCO filing. ATPCO stands for Airline Tariff Publishing Company, a company that collects and distributes fare data for the airline and travel industry. ATPCO fare rules use the following formats:

  • Long rules: The detailed fare rule text. Not supported by most NDC carriers.
  • Short rules: Abbreviated fare rules that summarize each rule category. These are usually high-level conditions better suited for use by experienced travel agents.
  • Structured rules: Structured rules limit the rules returned to one or more of these categories: advance reservation/ticketing requirements, minimum/maximum stay, stopovers, penalties, voluntary exchanges and refunds.

Fare Rules Support and Formats

The table below notes which types of rules are available for GDS and NDC using the standalone fare rules request. See the Fare Rules API Reference for endpoints and object descriptions.

For differences in support between GDS and NDC in the JSON APIs, see the support tables for seats, ancillaries, fare rules, and exchanges. Also see the NDC Carrier-Specific Notes and the NDC and GDS Functionality Comparison Chart.
For carrier-specific NDC differences, see NDC capabilities by airline through JSON API in the Travelport Knowledge Base. If you need login assistance, see Knowledge Base NDC Resources.

Fare Rule Type

Supported after Search

Supported after Price Supported for existing reservation

GDS

NDC

GDS

NDC

GDS

NDC

Short text fare rules

Yes

Yes

Yes

Yes

Yes

Yes

Long text fare rules

Yes

N/A (NDC carriers do not support long text fare rules)

Yes

N/A (NDC carriers do not support long text fare rules)

Yes

N/A (NDC carriers do not support long text fare rules)

Structured fare rules

Yes

Yes, Penalties only

Yes

Yes, Penalties only

Yes

Yes, Penalties only

When to Request Standalone Fare Rules

Per the support guidelines in the table above, you can send a fare rules request after your Search or AirPrice requests before making a reservation, or for an existing reservation.

Request after Search

Send a GET request per the Fare Rules API Reference with the identifiers from the Search response and the offer and product for which you want to return fare rules, and the fare rule type.

When standalone fare rules are requested after the Search response, they can be requested for one and only one product per request, using the productIDs query parameter.

Request after AirPrice

Send a GET request per the Fare Rules API Reference with the identifier from the AirPrice offer for which you want to return fare rules, and the fare rule type.

Request for Existing Reservation

Send a GET request per the Fare Rules API Reference with the reservation locator code for the reservation, and the fare rule type.

When standalone fare rules are requested for an existing reservation:

  • The booking must have been made using the JSON APIs.

  • The reservation must contain a valid fare and fare basis.

  • Not supported for split ticketing itineraries.

Fare Rules for Split Ticketing Itineraries

As explained in the Air Shopping Guide, split ticketing allows you to book a roundtrip ticket by sending two separate pricing solutions in one booking request. In other words, a split ticket has two separate one-way reservations instead of a single round-trip reservation.

You can request fare rules for a split ticket itinerary after either a Search or AirPrice request. Note the following limitations:

  • The response returns the rule number, tariff number and fare basis code only for long text and short text fare rules, not for structured rules.

  • If both offers have the same fare basis code and same rule number, the response returns the one fare rule that applies to both offers.

  • If the two offers have different fare basis codes with different rule numbers, for short and long text fare rules, flight details for the fare basis code for the first offer return the id values f1 and f2, and flight details for the fare basis code for the second offer also return f1 and f2.