Simplicity Through the Structured Fare Rules API

by

Structured-Fare-Rules-API

 

When issuing a ticket, common questions arise, such as: “how much will it cost to change it?” or “can I even refund it?” As the industry evolves, the rules and restrictions from the carriers become more complex. However, we can now provide a more efficient way to get information. The new Structured Fare Rules API enables customers to access the most relevant information for their travelers in a simplified and summarized way.

This API provides information regarding some of the rules including Change and Refund Information, Advance Purchase and Minimum and Maximum Stay. This way, the agency can utilize the information for internal purposes, like reducing the time travel agents spend reading and understanding rules, or even providing the information to the end customer. This enhancement will be delivered in 2 phases: one including Changes and Refund; the second one including Advance Purchase, Minimum and Maximum Stay. Phase 1 is currently ready for use, and we will introduce phase 2 in 2Q16.

As the information is coded, you can avoid language barriers by displaying the information in your native language. Simply program your systems to read the XML information and translate it into a user friendly display.

Additionally, the system also takes care of validation. This allows you to use it whenever needed, after Pricing, Shopping and even Ticketing. Once system receives all the information added on the RQ XML, it will look at all the different combinations of restrictions for your fare(s). If more than one fare is included, the system will return the most restrictive penalty for both change and refund. You just need to have the information to put on the Request; the rest is done on Sabre side.

All the details are informative purposes only and they might be subject to changes ones the change/refund/ticket is made.

For phase 1, you will be able to request change and refund information for the whole itinerary. The use case for an online consuming this API on its own (as opposed to shopping, where they can get it embedded) is simple to understand. It allows customers to call it whenever needed without having to invoke pricing or shopping again. For example, if you’ve created a PNR a month ago and want to price it today, you might not get the same fare, thus making it a different rule. In this case, if you have old information, you can call the service to have it validated. In addition, it allows the use of past date segments and the past date ticketing date to be validated.

Stay tuned for the second phase of the project, where we will introduce more rules and expanded information on changes and refund.

Structured Fare Rules service, StructureFareRulesRQ, is available in API version 1.0

Sample Workflow:

Step 1.* Compile fare information from Pricing or Shopping
OTA_AirPriceLLSRQ
BargainFinderMax (BFM)
BargainFinderPlus (WPNI)

Step 2. Call Structured Fare Rules service
StructureFareRulesRQ

Step 3. Display information as needed in your website or tool

*It should be noted the info in step 1 can be taken from any pricing/shopping service or host call. This example highlights common services.</>

XML Request/Response Example

Request:Response:

2 thoughts on “Simplicity Through the Structured Fare Rules API”

  1. Venket V says:

    This service very helpful to get refund penalty amount. but we can’t get text like below,

    ‘CANCELLATIONS PERMITTED FOR CANCEL.

    NOTE – TEXT BELOW NOT VALIDATED FOR AUTOPRICING.

    NIL CANCELLATION ON H CLASS AND ABOVE RAF 100

    PLUS JN TAX APPLICABLE ‘

    When we try we are getting 0 penalty amount but actual amount is 100 plus JN tax.

    1. Florencia Couto says:

      Hi Vanket,

      Thanks for your interest on this enhancement.
      Regarding the information that you are looking at, please note that it’s showing under NOTES. As in any other processing that we do in Sabre, the system will not be able to handle nor process them.
      All information that is coded above (so, actually present in the category, not as a text) will be consider for processing.

      Let me know if you have any further questions.

      Thanks,

      Florencia.

Leave a Reply

Your email address will not be published. Required fields are marked *