This method is available if you would like to provide route information through a web service or API.
Considerations for option three
Languages
The list of Origins and Destinations are typically saved by language. Sometimes an airline has different data by market, in the same language. We need to be clear from the beginning how many languages will be covered and what will be the market by default for each language.
Authorization
Usually, some type of authorization is needed to access the data. Some airlines use a token while others prefer to whitelist the PROS IPs. If authorization is required, we will need the Customer to provide an authorization token or key, or the means by which to generate this.
Display Format
The content displayed to end users is usually a combination of several fields, so PROS needs to understand how the information should be displayed.
Source
The customer must provide a source to access the list of valid Origins and Destinations. Usually, the customer provides an API or endpoint to get the information. When they do not have a specific endpoint, we can use route combinations collected from FareNet or airTRFX to dynamically generate the routes available, and the Core Dictionary for the location information that will be displayed.
Route Validation
Some airlines use the same list for Origins and Destinations, but many others load Destinations depending on the Origin selected.
Data Documentation
It is important to have the description of the data received. A detailed breakdown of the schema is helpful in interpreting the variables provided.
