How to exchange in valid way

[benys]

Dear OSDM Team,

I found at https://osdm.io/spec/state-models/ diagram:

please confirm that my way is ok:
a) passenger search exchange offers by: /bookings/{bookingId}/exchange-offers [don't pass detailed passanger, only anonimousPassengers]
b) selects best offer and create exchange operation by /bookings/{bookingId}/exchange-operations -> creates exchangeOperation [don't pass detailed passanger, only anonimousPassengers]
c) confirms exchange operation by /bookings/{bookingId}/fulfillments (bookingId is exchangeOperationId)

but I have question? how and when passenger can define purcharser details and passenger details?
for example: passenger wants to add new person / or replace persons..

Kamil

[jspetrak]

In the step A you defined new number and parameters of passengers, so you can specify the same passengers as originally booked, or completely different ages, reduction cards, ...

The exchange is performed on top of the original booking so there is currently no mean to change purchaser. That is retained as originally submitted for the booking.

[jspetrak]

Also, we are going to update the exchange diagram, see #691

[benys]

I understand but:

1. to confirm exchange have I execute normal booking fulfillment?
2. to set new first name and last name I have to use passenger API?(After creating exchange operation)?
   From my perspective is no consistent. During creating exchange operating we should pass passenger details same as creating normal booking.

[CGantert345]

1.: described in: https://github.com/UnionInternationalCheminsdeFer/OSDM/wiki/meeting-minutes-2022#2022-12-16-meeting
this will be added to the documention

2. Change of name would have to be made via the passenger API, but change of name might not be allowed or restricted by the provider due to tariff conditions.