# Retrieve reservation details

In all use cases, the **Actor** is the developer implementing the interface between the TripServices APIs and your company's application that provides travel results to your company's end users. **Actors** here are not searching/booking travel for themselves but instead are implementing this data handling for input from your company's travel customers.

#### Scope

This use case shows the code necessary to retrieve a booked reservation. The booking record contains all existing data on a reservation, including details for the room/s, traveler/s, form of payment and payment, terms and conditions, and locator codes.

| Prerequisites | Next steps |
|  --- | --- |
| - [Authentication](/docs/getting-started/authentication)
- An existing reservation created with the TripServices Stays APIs or another Travelport+ product, and the aggregator locator code/PNR for that reservation.

 | None. |


#### Use case

| Action | Goals and steps | Code Example |
|  --- | --- | --- |
| Request
 | Send a  Reservation Retrieve request:
1. In the  Reservation Retrieve request endpoint, send the aggregator locator code returned at booking  in Receipt/Confirmation/Locator/value.

Hotel bookings return multiple locator codes. For the aggregator code, at booking note the value in the instance of Receipt with Confirmation/Locator/locatorType=*PNR Locator*.  See [Locator Codes](/docs/stays/guides/stays-general-guide#confirmations-and-locator-codes) for more about locator codes.
 | Endpoint:
GET
https://api.travelport.com/11/hotel/book/reservations/K8TCLR
 |
| Response
 | The response returns all details currently on the booking.
You can confirm the correct booking was retrieved with the aggregator/PNR locator code returned in Locator/value, in the instance of Confirmation with locatorType *PNR Locator*
 | 
```json
 "Confirmation": {
     "@type": "ConfirmationHold",
       "Locator": {
            "value": "K8TCLR",
            "locatorType": "PNR Locator",
            "sourceContext": "Travelport",
            "creationDate": "2025-09-16"
            }
  }
```
 |