Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarification Needed on Linking Flight Details, Air Segments, Fare Information, and Air Price Points in LowFareSearchResponse #271

Open
Pdk3Dragon opened this issue Jan 6, 2024 · 0 comments

Comments

@Pdk3Dragon
Copy link

I am currently working on integrating the Travelport API, specifically the LowFareSearchResponse, into my project. I have successfully converted the API response from XML to JSON for better handling. However, I am facing challenges in understanding the relationship between certain key elements in the response.

In particular, I am looking for guidance on how to properly link the following elements:

1. FlightDetailsList
2. AirSegmentList
3. FareInfoList
4. AirPricePointList

I have thoroughly reviewed the API documentation, but I couldn't find explicit information on how these elements are related or how their data should be correlated.

To provide more context, I have attached both the original XML response and the corresponding JSON representation for your reference.

XML: LowFareSearchRsp.txt
JSON: LowFareSearchRsp.json

I would greatly appreciate any insights or guidance you can provide on how to establish the connections between FlightDetailsList, AirSegmentList, FareInfoList, and AirPricePointList. Understanding this relationship is crucial for processing and displaying accurate flight information within our application.

Thank you in advance for your assistance. I am eager to resolve this matter and continue integrating the Travelport API seamlessly into our project.

Best regards,
Althaf

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant