Rail Availability by Preferred Suppliers

By default, Rail Availability responses include solutions from all available suppliers (distributors). However, Rail Availability requests can be modified to include specified suppliers in a response.

Universal API uses the terms preferred, permitted, and disfavored to indicate filtering for suppliers. However, some providers and suppliers process only included or excluded suppliers:

For Rail Availability:

Request

Preferred suppliers can be requested either at an itinerary (journey) level. Supplier preferences for an entire journey are specified in RailAvailabilitySearchReq/RailSearchModifiers/PreferredSuppliers.

Note: Support for preferences within individual legs of a journey is available for Rail segments through Low Fare Shopping.

PreferredSuppliers weights the response to include the suppliers specified in the request. If there are no availabilities for the specified suppliers, other suppliers may be returned.

One or more Rail supplier values can be specified in instances of RailSupplier Code.

The value in the Code attribute is the two-letter rail distributor code. Currently, Universal API supports rail suppliers:

Response

A standard Rail Availability response is returned. The response is filtered at the data source to include or exclude the specified carriers or alliances.

Error and Warning Messages

The client must be provisioned for RCS and the rail distributor, and the two-letter Code must be valid, or an error is sent in the response.

The request fails if: