Overview
This Service provides the ability to retrieve an existing Order.
Itinerary details, such as Passenger, Ancillary, eTicket and EMD details are all returned in the OrderViewRS.
NDC Schema: IATA OrderRetrieveRQ & OrderViewRS v21.3.
Pre-condition(s)
- Existing OrderID or Booking Reference (PNR), or GDS PNR (VS PNR only)
- This service can only be used on existing bookings and can only be accessed by the Seller who created the Order (via same aggregator, where applicable)
- Requestors (Travel Agency, Meta-Search, TMC) must have an agreement with Virgin Atlantic
In Scope
Request
-
Existing OrderID or Booking Reference or GDS PNR (VS PNR only)
Response
-
OrderID with a Booking Reference/PNR
-
e-Ticket document per Pax(s) or/and EMDs
-
Passenger/Individual details (name, date of birth, gender, email address, and phone) along with Frequent flyer number
-
Flight details with previously selected seats
-
Total Order price (Flight + Ancillaries) with tax breakdown
-
Order Item price with tax breakdown
-
Unticketed Order (Hold Booking)
-
Original ticket details (for bookings containing reissued tickets)
-
Passenger APIS details
-
India GST
Out of Scope
- Group Booking
- Personalized Offer
- Redemption
Endpoints
Sandbox Environment
This is a complete replica of production and a test environment where developers can build against our NDC APIs and validate their code for build of new features, ahead of certification and go-live. This environment should also be used for debugging
Preview Environment
This environment will have the same capability features as Sandbox but in addition we may deploy breaking changes or new features in advance of release to Sandbox and Production in order to give developers early visibility.
https://ndcdeveloper.virginatlantic.com/SalesAndRevenueManagement/OrderShopping/OrderManagement/v2/OrderRetrieve
https://ndcdeveloper.virginatlantic.com/preview/SalesAndRevenueManagement/OrderShopping/OrderManagement/v2/OrderRetrieve
Business Rules
ID <-> RefID Syntax/Format
ID <-> RefID attribute request/response formats are shown as follows:
| ID |
RefID |
Syntax |
Example |
| PaxJourneyID |
PaxJourneyRefID |
"JOUR"+<number counter> |
JOUR1 |
| PaxSegmentID |
PaxSegmentRefID
SegmentRefs |
"SEG"+<number counter> |
SEG1 |
| PaxID |
PaxRefID
PassengerRefs |
Refer PaxID based on PTC |
ADULT_1 |
| ServiceID |
ServiceRefID |
"SV"+<number counter> |
SV1 |
| ServiceDefinitionID |
ServiceDefinitionRefID |
"BAGSRV"+<number counter> |
BAGSV01 |
| BaggageAllowanceID |
BaggageAllowanceRefID |
"BAGA"+<number counter> |
BAGA1 |
GDS PNR
PNR created in a GDS (with VS Flight segment) can be used to retrieve the booking details. Only the VS booking reference can be used to retrieve the booking. If the booking doesn’t have VS ticket (932), the booking will not be returned.
Feedback for this page? How was your experience? Please click
here
