Special Service Request (SSR) Error Messages

Special Service Request (SSR) Error Messages

Special Service Request (SSR) Error Messages

This page contains examples of the Errors that can be returned by our API when including Special Service Requests.

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 will always be shown in the applicable response message (ServiceListRS, OrderViewRS).

 

Scenarios

Scenarios

Scenario 1 - SSR requested in OfferPrice and then also in ServiceList

Formerly, these services could only be requested in the OfferPrice Service, and subsequently booked in OrderCreate. As explained in our Special Service Request page, they can now be requested in both the OfferPrice and the ServiceList messages. We recommend any new developments use the ServiceList, and those using the OfferPrice migrate to the ServiceList asap, as any new Special Services offered will more than likely only be offered through the ServiceList API.

 

OfferPriceRQ /ServiceListRQ

OrderViewRS

OfferPriceRQ /ServiceListRQ

OrderViewRS

If you request the Special Services in the OfferPrice, and then you erroneously also request them also in the ServiceList, which are both requested in the same manner using the SpecialNeedQualifiers:

<Qualifier> <SpecialNeedQualifiers> <Code>DEAF</Code> </SpecialNeedQualifiers> </Qualifier>

 

If you use the ALaCarteOfferItem OfferItemID from the OfferPriceRS after having erroneously also done a ServiceListRQ, then the following error will be returned:

<Errors> <Error ShortText="SSE_ORM_900524" Code="795">The service selected is incorrect. Please try again and, if the issue persists, please contact us.</Error> </Errors>

If you use the ALaCarteOfferItem OfferItemID from the ServiceListRS then the Order will be created with the Special Services required:

<OrderItem OrderItemID="IB3af237191cc24767bffa121f81bf0c18OC_05"> <PriceDetail> <TotalAmount> <SimpleCurrencyPrice Code="EUR">0.00</SimpleCurrencyPrice> </TotalAmount> <BaseAmount Code="EUR">0.00</BaseAmount> <Taxes> <Total Code="EUR">0.00</Total> </Taxes> </PriceDetail> <Service ServiceID="SPECIAL_NEED_IB382720231015_04" ServiceStatus="HK"> <PassengerRef>ADULT_01</PassengerRef> <ServiceDefinitionRef SegmentRef="IB382720231015">SPECIAL_NEED-DEAF</ServiceDefinitionRef> </Service> <Service ServiceID="SPECIAL_NEED_IB383620231008_03" ServiceStatus="HK"> <PassengerRef>ADULT_01</PassengerRef> <ServiceDefinitionRef SegmentRef="IB383620231008">SPECIAL_NEED-DEAF</ServiceDefinitionRef> </Service> </OrderItem>

Scenario 2 - SSR Code is NOT valid

The SSR code introduced is not among the ones listed in this table or is incorrect.

ServiceListRQ / OfferPriceRQ

ServiceListRS

ServiceListRQ / OfferPriceRQ

ServiceListRS

In ServiceListRQ, the code DPNA ir incorrectly spelled in this case:

Error returned in ServiceListRS:

 

Scenario 3 - SSR requested in Post-Sale flow

Special Service Requests are NOT available in Post-Sale scenarios.

ServiceListRQ

ServiceListRS

ServiceListRQ

ServiceListRS

In ServiceListRQ with Order, we request the SSR code for Wheelchair for Steps (WCHS):

Error returned in ServiceListRS:

 

For further information about all kind of error messages, please go to the following link:

Error Codes

 

Â