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

Exchange at PAX level . How to use Post/ /bookings/{bookingId}/exchange-offers #759

Open
TOP-PHE opened this issue Nov 22, 2024 · 0 comments
Assignees
Labels
documentation Improvements or additions to documentation
Milestone

Comments

@TOP-PHE
Copy link
Collaborator

TOP-PHE commented Nov 22, 2024

I see the AnonymousPassengerSpecification/externalRef* as being mandatory as well as the passenger type.

In the case of a railway that does not allow to change the Pax but only the trip (like changing the hour of the trip to the next train...), having the external ref of the PAX is normal, as it will be used to calculate the new offers.......but why in this case to have passenger type mandatory as the passenger type is already defined in the Railway system and can be found with the External ref ?

In the second case of an exchange of the Pax (Same trip but a different PAX), why to have the externaref PAX as mandatory at the moment of the offer request.

I see only one explanation on my side;
The external ref element is used to identify which PAX will be exchanged in the current booking (if for example you have 5 PAX in one fullfilment (in airline it is much simpler One PAX, one fullfilment for everybody...) but it is ilogical, as it is flagged as being an info used for OfferSerarch in the way the object is structured.

Can you provide more explanation on how thhose lements are used ?

@TOP-PHE TOP-PHE added the documentation Improvements or additions to documentation label Nov 22, 2024
@TOP-PHE TOP-PHE self-assigned this Nov 22, 2024
@TOP-PHE TOP-PHE added this to the 4.0.0 milestone Nov 22, 2024
@jspetrak jspetrak moved this to To do in OSDM Specification Dec 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
Status: To do
Development

No branches or pull requests

1 participant