What is it?
This method is used to create or update a Sabre PNR in an active session based on the provided vendor reservation.
If an active session already contains a Sabre PNR based on the same vendor reservation, the Sabre PNR will be updated with new information. This allows developers to merge back changes in the vendor reservation after changes take place. For example, after ticketing or refund processes.
Why use it?
Use this method to reflect the state of a vendor reservation in a Sabre PNR.
How it works
Create or update a Sabre PNR in an active session based on the vendor reservation. The Sabre PNR is kept open after the operation.
Note: The Sabre PNR contains passive rail segments, and changes to the Sabre PNR will not be reflected in Rail vendor systems.
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
The request body is empty.
Returns warnings, if any, or no data upon success. The Sabre PNR created or updated by this operation will be open in an active session.