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

Unsuccessful primary host transaction causing reservation failure #227

Open
rj001-10 opened this issue Nov 23, 2021 · 3 comments
Open

Unsuccessful primary host transaction causing reservation failure #227

rj001-10 opened this issue Nov 23, 2021 · 3 comments

Comments

@rj001-10
Copy link

Hello,

When doing an AirCreateReservationReq, I am getting an Unsuccessful primary host transaction causing reservation failure error. Below are my Galelio credentials and the request XML. I would really appreciate your help.

Universal API User ID: Universal API/uAPI3530284402
Branch Code (TargetBranch) for ProviderName (ProviderCode): Branch Code for Galileo (1G): P105392

XML REQUEST: is attached
xmreq.txt

And also Tried my credentials with demo site but it show error it also attached with this issue with air pricing stage:
tger

Can you please help me.

@RicOsiro
Copy link

hi,

it could be problem on the environment. It is not a production, so some data are old or invalid in some components.
Please, could you try different route, date or even a brand?
I've just created a booking on the same flight and date but in Economy Flex Plus. LOC 162IW6, you could retrieve it on demo site using the default credential pre-production.

your request (AirCreateReservationReq) is similar to demosite xml request, but in version 51. It should work. The credential seems not be a issue, you could get response on fare search.

thanks and regards

@rj001-10
Copy link
Author

Thank you, I have one more doubt , which are the minimum inputs needed to perform AirCreateReservationReq?

@RicOsiro
Copy link

hi,

the minimum inputs is general way are: passenger and contact, a segment and ticket arrangement. In XML request, they are not a unique value, they are object with many attributes that are XML elements and XML attributes. Also it depends on the market and carrier that request some extra parameters, but they are flagged as optional on the schema and help.
The summary inputs are BookingTraveler, AirPricingSolution/AirSegment and ActionStatus. The AirPricingSolution/AirPricingInfo is not mandatory to create a booking, but normally it is included to have the right price, it could change fast.
The online help pages are the details about these parameters, if they are mandatory or not. On the beginning it is a good idea to send only the minimum values, after that to increase the complexity according to the business need. The soap api is very robust to support the business.

thanks ana regards

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

2 participants