-
Notifications
You must be signed in to change notification settings - Fork 191
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
Why the header needs 4.0 record locator? #253
Comments
In which moment record locator needed? |
Hi! What's happening: I'm trying to configure 4.0 header configuration for use in the project. However, following the related step that link here, says it's necessary to use the record locator, but didn't understand why or where to get this information. My code is equal to the referenced in the link. |
Soap header 4 does not need record locator. I guess you've just started to work with Amadeus. What you want to implement at all? |
Exactly! Is my first attempt at setting and just been informed, by the support of Amadeus, which was necessary to setup header 4.0. But I don't know where to start, I confess. I need to call airline services, as a search engine: search the itinerary, get rates, select the offer and booking. It takes the header? It's used for these searches, correct? |
Start with learning of Amadeus session management: header implementation guide, sessions best practices. Then I guess is the best to start with Amadeus WBS Implementation Guide which you can find at Also you should know some things, so read this comment from creator of this repo: #240 (comment), and this may be helpful to you when implementing Search with |
@therealartz, thank you!! I'll start this study to make the correct implementations. |
Hi, If your original question is answered, you may close this issue. |
Hello! Could you help me?
I'm trying to accomplish the implementation of header 4.0 for my project of Amadeus.
However, I would like to understand why you need the record locator and where I could capture that information, because I couldn't find in the documentation.
The text was updated successfully, but these errors were encountered: