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.

Sign up for GitHub

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

Jump to bottom

#691 Exchange Flow description expanded #724

Merged
merged 1 commit into from
Oct 10, 2024
Merged

#691 Exchange Flow description expanded #724

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 11 additions & 1 deletion spec/processes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1105,6 +1105,16 @@ Requesting an exchange offer is almost identical to requesting a standard offer.
The only difference in the request is that the fulfillment that the API consumer
wants to exchange, and an overrule code if relevant, are also provided.

The exchange flow is following:

- `POST /exchange-offers` to get alternative exchange offers (exchange operations) for the given fulfillments
- `POST /bookings/{bookingId}/exchangeOperations` with selected exchange offer with a. information what to change on current booked offers, or b. to put a new offer (exchange operation) to the booking
- `PATCH /bookings/{bookingId}/exchangeOperations/{exchangeOperationId}` to confirm the exchange. This will release the original booking parts and confirm parts offered in the exchange operation.
- `POST /bookings/{bookingId}/fulfillments` to issue the new fulfillments for exchanged booking parts.
- Optionally `PATCH /bookings/{bookingId}/fulfillments` if the asynchronous fulfillment requires that.

It is a good practice to execute `DELETE /booking/{bookingId}/exchangeOperations/{exchangeOperationId}` to terminate the exchange operation without confirmation and release booked offers from the operation.

### Replacement of lost tickets and cards

The replacement is used to replace physical cards and tickets. There is no
Expand All @@ -1113,7 +1123,7 @@ replacement for electronic tickets or anonymous tickets.
#### Requesting a replacement for a lost ticket

The replacement is requested similar to the request for a non-trip based offer.
The search tags must include the key word CARD_LOST or TICKET_LOST. The provider
The search tags must include the key word `CARD_LOST` or `TICKET_LOST`. The provider
will ask for the required data of the lost card or ticket to be provided with
the passengers card data (card number).

Expand Down