Queueing Tickets
Prior to ticketing, you can add queue placement information to a PNR. This adds a specific agency queue to the reservation so that any additional action can be managed as necessary. Queue placement is optional and takes place in a workbench session, either standalone or as part of ticket issuance.
In this topic:
- Queue Placement Request
- Queue Placement Response
- Queue Placement Request Example
- Queue Placement Response Example
Queue Placement Request
Query Parameters
None.
POST Request
Send the POST request to the following resource:
POST queue/queue
Base path:
Pre-production https://api.pp.travelport.com/9/air/
Production https://api.travelport.com/9/air/
Payload
The message payload sends the PNR and queue information.
Parameter | Description | Required | Optional |
---|---|---|---|
AgencyQueue
|
Top level object for request. |
None
|
None |
ReservationIdentifier |
PNR
|
value: PNR of the reservation to add to the queue. |
None |
Queue |
Queue details. Multiple instances of Queue can be sent. Each instance of Queue is one individual queue. |
value: Queue number. |
category: Customer-defined category within a queue. dateOffset: Numeric value for a date range. date: Date and time for a specific customer-defined action within that queue. pccOverride: PCC to override the agency default PCC for that queue. |
Queue Placement Response
The response returns a confirmation that the transaction was successful.
Example Queue Placement Request
{
"AgencyQueue": {
"ReservationIdentifier": {
"value": "6Q04QC"
},
"Queue": [
{
"pccOverride": "79JP",
"value": "67"
}
]
}
}
Example Queue Placement Response
The response returns a status confirmation per below.
{
"BaseResponse": {
"Result": {
"status": "Complete"
}
}
}