Queue Placement API Reference
POST |
queue/queue Base path: Pre-production https://api.pp.travelport.com/11/air/ Production https://api.travelport.com/11/air/ |
Related Content: Ticketing Guide
Prior to ticketing, you can add queue placement information to a reservation. This adds a specific agency queue to the reservation so that any additional action can be managed as necessary. Queue placement is optional after booking A confirmed reservation with the carrier. A held booking is a reservation that has not yet been ticketed. The terms booking and reservation are interchangeable. and before ticketing.
This is one of two ways to specify a queue. Alternately, you can send an optional payload to specify a queue at booking at Workbench Commit.
Request
Also see Authorization and Common Headers.
Query Parameters
None.
Request Body

Object |
Description |
Required/Optional |
---|---|---|
AgencyQueueSummary |
Top level object for request. |
Required |
ReservationIdentifier |
Top level object. |
Required |
|
Locator code of the reservation to add to the queue. |
Required |
Queue |
Queue details. Multiple instances of Queue can be sent. Each instance of Queue is one individual queue. |
Required |
|
Queue number. |
Required |
|
Customer-defined category within a queue. |
Optional |
|
Numeric value for a date range. |
Optional |
|
Date and time for a specific customer-defined action within that queue. |
Optional |
|
PCC |
Optional |
Response

Object |
Description |
---|---|
BaseResponse |
Top level object. |
Result |
Top level object. |
|
Status of queue placement. |
Example Request

{
"AgencyQueue": {
"ReservationIdentifier": {
"value": "6Q04QC"
},
"Queue": [
{
"pccOverride": "79JP",
"value": "67"
}
]
}
}
Example Response

{
"BaseResponse": {
"Result": {
"status": "Complete"
}
}
}