What is it?
This method returns Rail offers for the inbound portion of a round trip.\ Note: An outbound offer id is required to return appropriate inbound offers.
The round trip shopping process consists of two steps - one for outbound offers, and one for inbound offers.
Returned inbound offers have the same structure of information found using the
POST /v1/rail/offers/journeys method.
Why use it?
Use this method to get inbound offers from Rail vendors for a round trip.
This is the second step in the two-step process of requesting round trip offers. These offers are then used to create orders as part of the
POST /v1/rail/orders method.
How it works
- Specify two search criteria to search by in the request, one for an outbound trip and the second of an inbound trip. The outbound
offerIdmust be specified in the request.\ Note: This is similar to the
POST /v1/rail/offers/journeysmethod, except you'll provide outbound and inbound criteria, instead of a single criteria.
- The response returns only inbound offers presented in the same way as the
Caution: Consuming this API and its content requires special permission. Before requesting access please make sure you have all the necessary agreements in place with the rail vendor(s) you would like to sell using Content Services for Rail. For more information on accessing Sabre Rail content and rail supplier contacts please visit the respective product page on Sabre Central.
|Vendor||Code||Payment via API||Notes|
|SNCF||2C||No||“On account” only. Direct settlement with agency. No individual or corporate credit cards.|
How to use
In addition to the required
marketingCarrierCode, provide two search criteria elements containing:
- From/to station codes
- Departure/arrival date and time
- Number of passengers, type, and any linked discounts
This request handles the inbound direction for a round trip.
Returns a list of offers, including the unique
offerId, and all other details needed to create an order for the inbound portion of a round trip.