Create Reservation (Full Payload) or Sync Hotel Reservation
Use the Create Reservation Full Payload request to book a room by sending complete stay details and the booking code from the Availability response, along with traveler, form of payment, and payment information. NOTE: Availability results are stored in cache for 30 minutes. If the offers expire before you create a reservation, you must send a new request before booking. The Create Reservation Full Payload response uses the same format as the reference payload response. The only difference is that the Reference Payload response returns Reservation/id, which is the offer ID sent in that request. The full payload response does not return this information. Note for Multi-room sell requests- when making a reservation, Travelport attempts to sell the number of rooms requested; however, the supplier may not be able to accommodate the total number of rooms. Each room sold creates a unique hotel segment on the Travelport reservation. A traveler name is associated with each room with these limitations: If the number of rooms requested is equal to the number of traveler names in the request, each room is associated with a unique traveler name. If the number of rooms requested is not equal to the number of traveler names in the request, all rooms are associated with the first traveler name. Note for query parameters- Hotel APIs that create a new reservation or add to an existing one verify the reservation request with the guarantee type and price returned in preceding workflow steps. If there is any difference, the API does not yet create the reservation but instead returns an error to notify about the change. To accept the change, send the request a second time with the applicable query parameter/s (acceptPriceChangeInd and/or acceptGuaranteeChangeInd). Do not send either of these query parameters in the initial request. If you do not want to proceed with the booking because of the changes, you are not required to send a second booking request with the false value(s). You can simply let these offers expire. Use the Sync Reservation request to synchronize a Booking.com hotel reservation to a Travelport PNR whenever specific sell failures occur. The Sync Reservation request is a scaled down re-try of a previous Create or Add Reservation request that adds to the original sell request the Traveler email address and the Booking.com booking information. The Sync message attempts to add the reservation information into a Travelport reservation as a standard aggregator segment but without re-selling the segment in the aggregator system. Booking.com requires the traveler email address in a hotel sell request. If the sell completes in the Booking.com system, the traveler receives a confirmation email containing information needed to synchronize the Travelport booking if the user receives one of two specific error messages on the original sell attempt. The Sync Reservation response returns all available data for the reservation using the same structure as the Create Reservation response.
Query parameters
Send with true to accept any difference in the current sell price from the total price returned in an earlier response. Default is false; terminates the sell process without booking. Create Reservation only.
Send with true to accept any difference in the guarantee type from the guarantee type returned in an earlier response. (The guarantee types checked for differences are guarantee required, deposit required, prepay required.) Default is false; terminates the sell process without booking. Create Reservation only.
If true, the user expects that the sell request will be failed if any of the requested reservation comments fail. If indicator is not sent the service will default to false.
If true, the multi-room request will be sold as a separate reservation per traveler. If indicator is not sent the service will create a single reservation for all travelers. Default is false.
Headers
Used in hospitality workflows to provide a Unique transaction or tracking id for a single request and response.
Identifies the Travelport access group with which the caller is associated
Allows user to pass PCC instead of Access Group ID
Identifier used to correlate hotel API invocations across a multi-call business flows.
Request body
Response
OK - Successful Response - 200
Example response
{
"ReservationResponse": {
"Reservation": {
"@type": "Reservation",
"id": "REF12873",
"Identifier": {
"value": "A0656EFF-FAF4-456F-B061-0161008D7C4E",
"authority": "TVPT"
}
},
"@type": "response",
"transactionId": "49f58f5f-c443-43b4-9f5d-be405fd00a01",
"traceId": "TraceID_123456",
"Result": {
"@type": "Result",
"status": "Complete",
"Error": [
{
"@type": "ErrorDetail",
"StatusCode": 200,
"Message": "No flights found.",
"NameValuePair": [
{
"value": "Sunday",
"id": "6",
"name": "Day1"
}
]
}
],
"Warning": [
{
"@type": "WarningDetail",
"StatusCode": 200,
"Message": "Customer Loyalty could not be applied.",
"NameValuePair": [
{
"value": "Sunday",
"id": "6",
"name": "Day1"
}
]
}
]
},
"Identifier": {
"value": "A0656EFF-FAF4-456F-B061-0161008D7C4E",
"authority": "TVPT"
},
"NextSteps": {
"id": "5",
"NextStep": [
{
"value": "www.resourcelocation.com",
"id": "2",
"action": "cancel",
"description": "remove offer from the order"
}
]
},
"ReferenceList": [
{
"@type": "ReferenceListFlight"
}
],
"CurrencyRateConversion": [
{
"SourceCurrency": {
"value": "USD",
"codeAuthority": "ISO 4217",
"decimalPlace": 4,
"decimalAuthority": "ISO 4217"
},
"TargetCurrency": {
"value": "USD",
"codeAuthority": "ISO 4217",
"decimalPlace": 4,
"decimalAuthority": "ISO 4217"
},
"ConversionRate": {
"rateAuthority": "ISO 4217",
"rateAsOf": "2026-08-07T12:12:00Z"
}
}
],
"Pagination": {
"@type": "Pagination",
"page": 1,
"pageSize": 20,
"totalPages": 5,
"totalItems": 100
}
}
}