Ancillaries Errors and Warnings
Ancillaries Errors and Warnings |
|---|
This page contains examples of the Errors and Warnings that can be returned by our API when purchasing Ancillaries.
The texts are returned in Spanish or English, which is the default language. Localization of the text can be undertaken by the Seller/Aggregator based on the Short-text code.
Errors and Warnings will always be shown in the applicable response message (ServiceListRS, SeatAvailabilityRS).
Given the inclusion of new Ancillaries in the ServiceList, (available in the Pre-Sale and on hold flow), the handling of errors and warnings has undergone changes in the following scenarios:
If Offers are returned for only some of the requested Services, warnings also will be included for those Services which are not available.
If all of the requested Services fail, an Error will be returned for each failed Service.
In the event of several Warnings referencing the same Ancillary/Service, they will be grouped together.
ServiceList Pre-Sale Flow |
|---|
Scenario 1 - Invalid ServiceFilter Group Code
ServiceListRQ sample The ServiceFilter introduced is incorrect: | ServiceListRS sample The returned error is: |
|---|---|
<Parameters>
<ServiceFilters>
<ServiceFilter>
<GroupCode>AF</GroupCode>
</ServiceFilter>
</ServiceFilters>
</Parameters> | <Errors>
<Error ShortText="NDC_DIST_1014" Code="486">Service Filter is not valid</Error>
</Errors>
|
ServiceListRQ sample Mixing valid and invalid ServiceFilter GroupCodes: | ServiceListRS sample The invalid ServiceFilter returns the following warning: |
|---|---|
<Parameters>
<ServiceFilters>
<ServiceFilter>
<GroupCode>BG</GroupCode>
</ServiceFilter>
<ServiceFilter>
<GroupCode>TS</GroupCode>
<SubGroupCode>PX</SubGroupCode>
</ServiceFilter>
</ServiceFilters>
</Parameters> | While the Offers from the valid ServiceFilter are returned: |
Scenario 2 - Pre-Sale Flow mix of Services available and not available
ServiceListRQ sample Mixing available and not available Services: | ServiceListRS sample The non available ServiceFilter returns the following warning: |
|---|---|
While the Offers from the available ServiceFilter are returned: |
ServiceList Post-Sale Flow |
|---|
Scenario 1 - Inclusion of ServiceFilter (Not available in Post-Sale Flow)
ServiceListRQ sample ServiceFilter parameters are not valid for Post-Sale: | ServiceListRS sample The returned error is: |
|---|---|
ServiceListRQ sample Purchase of Bags in a Post-Sale scenario: | ServiceListRS sample The returned error is: |
|---|---|
|
SeatAvailability Flow |
|---|
Scenario 1
Error message displayed due to non-availability of Seats:
SeatAvailabilityRS sample Non-availability of Seats. The returned error is: |
|---|
Unpaid / on hold |
|---|
The following are the errors that you may encounter when trying to book and pay for ancillaries.
Unpaid Orders
The following is the error return if you try to pay for an order (with flights and seats) where the seat has been cancelled. In this case you need to retrieve the order (which will be returned only with the services that are not cancelled and can be pay for) before sending the OrderChange Payment.
OrderChange Payment error response example You have tried to paid for seats that are no longer booked. The returned error is: |
|---|
The following error is returned when you try to book seats in an Unpaid Order (flight tickets yet to be issued). The Order with the flights and any confirmed ancillaries must be paid for and issued first, and then the seats can be added to the Order and paid for.
SeatAvailabilityRS sample Purchase of Seats in a Post-Sale scenario. The returned error is: |
|---|
SeatAvailabilityRS sample Purchase of Seats in a Post-Sale scenario. The returned error is: |
|---|
For further information about all kind of error messages, please go to the following link:
