The Go live Certificate there is an issue get it from travelport tech support

[MohammaedAlani]

When attempting to obtain a live credential through Travelport support, I encountered an issue that requires obtaining a certificate. However, despite sharing logs for the entire flow (LFS - AirPrice - Book) with the technical support team, I did not receive the certificate. I am concerned about whether it is possible to obtain a certificate using this SDK for Travelport. If anyone has successfully obtained a certificate using this SDK, I would appreciate any insights or guidance.

Thank you for your ongoing support.

This is comment for travelport

Pricing-
AirSegment@Connection Indicator - I noticed you have not passed correct connection indicator.
<air:AirSegment Key="VZfhDkSqWDKAqgTLaAAAAA==" Group="0" Carrier="QR" FlightNumber="4" Origin="LHR" Destination="DOH" DepartureTime="2023-10-10T15:05:00.000+01:00" ArrivalTime="2023-10-10T23:50:00.000+03:00" FlightTime="405" Distance="3246" ETicketability="Yes" Equipment="388" ChangeOfPlane="false" ParticipantLevel="Secure Sell" LinkAvailability="true" PolledAvailabilityOption="Cached status used. Polled avail exists" OptionalServicesIndicator="false" AvailabilitySource="Q" AvailabilityDisplayType="Fare Shop/Optimal Shop">

</air:AirSegment>
<air:AirSegment Key="VZfhDkSqWDKAtgTLaAAAAA==" Group="0" Carrier="QR" FlightNumber="948" Origin="DOH" Destination="SIN" DepartureTime="2023-10-11T02:40:00.000+03:00" ArrivalTime="2023-10-11T15:45:00.000+08:00" FlightTime="485" Distance="3857" ETicketability="Yes" Equipment="359" ChangeOfPlane="false" ParticipantLevel="Secure Sell" LinkAvailability="true" PolledAvailabilityOption="Cached status used. Polled avail exists" OptionalServicesIndicator="false" AvailabilitySource="Q" AvailabilityDisplayType="Fare Shop/Optimal Shop"/>
<air:AirSegment Key="VZfhDkSqWDKAloTLaAAAAA==" Group="1" Carrier="QR" FlightNumber="947" Origin="SIN" Destination="DOH" DepartureTime="2023-10-20T21:00:00.000+08:00" ArrivalTime="2023-10-20T23:45:00.000+03:00" FlightTime="465" Distance="3857" ETicketability="Yes" Equipment="359" ChangeOfPlane="false" ParticipantLevel="Secure Sell" LinkAvailability="true" PolledAvailabilityOption="Cached status used. Polled avail exists" OptionalServicesIndicator="false" AvailabilitySource="Q" AvailabilityDisplayType="Fare Shop/Optimal Shop"/>

</air:AirSegment>
<air:AirSegment Key="VZfhDkSqWDKAnoTLaAAAAA==" Group="1" Carrier="QR" FlightNumber="105" Origin="DOH" Destination="LHR" DepartureTime="2023-10-21T01:05:00.000+03:00" ArrivalTime="2023-10-21T06:25:00.000+01:00" FlightTime="440" Distance="3246" ETicketability="Yes" Equipment="77W" ChangeOfPlane="false" ParticipantLevel="Secure Sell" LinkAvailability="true" PolledAvailabilityOption="Cached status used. Polled avail exists" OptionalServicesIndicator="false" AvailabilitySource="Q" AvailabilityDisplayType="Fare Shop/Optimal Shop"/>

AirCreateReservationReq-
AirSegment@Connection Indicato- See my comment on pricing.

[nmbabor]

I also need this solution, I have faced same issue.

[MohammaedAlani]

@nmbabor There is currently no available solution for that particular issue. I do, however, have an additional concern regarding this matter. I am wondering if this SDK is capable of effectively functioning within a production environment. It is of utmost importance that it can seamlessly generate and manage tickets without encountering any obstacles.

[kommandant-topp]

Hello @MohammaedAlani,
Could you, please, attach LFS response that you were using for the booking creation?

Thank you, and have a nice day!

[MohammaedAlani]

Hi @kommandant-topp

I am currently in the live environment, and I have encountered the following situation. I resolved the problem using Travelport UAPI directly. Now, let me summarize the issue I encountered during the normal booking flow: LFS -> GetPrice -> Book.

1. On LFS need to add Age for Infant in the search request. for example child you are putting 9, but for infant must putting also a value like age=1.

2. On Get Price => Air segment information should be passed as received in the LFS rsp to the Air Price/Create.

EX:

3. Air Pricing Req-
   1)AirItinerary@AirSegment - ClassOfService is not recommended in AirSegment.
   2)AirItinerary@AirSegment - You have not used some of the attributes in AirSegment as returned in LowFareSearchRsp like
   OptionalServicesIndicator, AvailabilityDisplayType etc. Please use the air segment exactly as returned in LFS response, and
   do not edit any information. ClassOfService is not recommended in AirSegment.

4. Air Create Reservation Request-
   1)AirItinerary@AirSegment-See my comment above in AirPriceReq.
   2)AirPricingSolution/AirPricingInfo - You have not passed complete AirPricingSolution@AirPricingInfo in your request.
   Please pass complete AirPricingSolution in your booking request as returned from the previous AirPriceRsp. Like I notice
   that there are 4 BookingInfo returned in AirPriceReq in AirPricingSolution\AirPricingInfo, but you have passed only one in
   your booking request. Similarly you have not passed TaxInfo as well. Please pass complete AirPricingSolution in your
   booking request along with AirPricingInfo.
   3) BookingTraveler@NameRemark ñ You have not included NameRemarks for INF booking travelers in your request.
   Name remarks are recommended for INF. You can check more details on name remarks here:
   https://support.travelport.com/webhelp/uapi/uAPI.htm#Booking/Shared_Topics/Name_Remarks.htm

   Format for infant name remarks:
   Infant NameRemark
   
   DOB13MAR22
   

   4)SSR for infant - the airline will know who is holding the infant. The SSR DOCS item is entered as normal with the addition
   of an "I" after the gender. Please use SSRs as a part of certification process as its required by some carriers/sectors.
   You can find detailed information about how to use SSRs here:
   https://support.travelport.com/webhelp/uapi/uAPI.htm#Air/Shared_Air_Topics/SSRs_(Special_Service_Requests).htm#Infant

After fixed these issue get another one also.

Pricing-
AirSegment@Connection Indicator - I noticed you have not passed correct connection indicator.

// this is from your SDK request
<air:AirSegment Key="VZfhDkSqWDKAqgTLaAAAAA==" Group="0" Carrier="QR" FlightNumber="4" Origin="LHR" Destination="DOH" DepartureTime="2023-10-10T15:05:00.000+01:00" ArrivalTime="2023-10-10T23:50:00.000+03:00" FlightTime="405" Distance="3246" ETicketability="Yes" Equipment="388" ChangeOfPlane="false" ParticipantLevel="Secure Sell" LinkAvailability="true" PolledAvailabilityOption="Cached status used. Polled avail exists" OptionalServicesIndicator="false" AvailabilitySource="Q" AvailabilityDisplayType="Fare Shop/Optimal Shop">

</air:AirSegment>

And there is another issue related to that.

[kommandant-topp]

Hello @MohammaedAlani,
I'm happy to hear that you've got live credentials from Travelport!

Do you consider contributing fixes for those issues?
Check our contribution instruction.

Thank you, and have a nice day!