What is it?
In detail: this suite of utility APIs allows you to create (and modify) a custom response view by defining the response paths to include or exclude for a given REST API (e.g. the Bargain Finder Max (BFM) API). You would then pass your custom response view as a filter in the BFM API request, e.g.,
view=NOWARNINGS to format the response.
A custom response view is a view defined by a single Pseudo City Code (PCC). This is created by modifying a default Sabre response view or creating a new response view. By default, the API allows you to create up to 100 custom response view definitions per Pseudo City Code (PCC) and include or exclude up to 1000 paths per response
Response views can be used with the following APIs: Advanced Calendar Search, Alternate Airport Shop, Alternate Date, Bargain Finder Max, InstaFlights Search.
Why use it?
You could use this suite of APIs to create a custom response view for the Bargain Finder Max API that trims the response to include only the response paths that your application requires.
How to use?
Custom response view data disclaimer
Sabre® creates and maintains a list of default response view definitions and their corresponding include and exclude paths in the Sabre cache. This API allows you to view and customize response view definitions, including default Sabre response views.
A custom response view is a view defined by a single Pseudo City Code (PCC). This is created by modifying a default Sabre response view or creating a new response view. All modifications to any Sabre response view or custom response view, and the corresponding response paths, are mapped to and accessible by a single PCC. A PCC stores private data that is unique to a specific customer of which is determined during authentication to REST APIs. Custom response views cannot be shared or used by other PCCs. Only the PCC that created a custom response view or modified a Sabre response view can use those custom views.
Important: We strongly suggest that customers do not modify a Sabre response view and that customers create unique names for their custom views. Once a Sabre response view definition is modified, any updates to that response view will no longer be inherited. It would, therefore, be entirely up to the customer to manually maintain that view. For example, if you associate a new response view to the Sabre OTA_AirLowFareSearchRS.Warnings response view, then your response view will not inherit any new included or excluded paths that Sabre associates to the response view in the future.