OTST_TI_RFND_2PAX_1REFUND

[LucFen]

Description
Scenario includes:
• Post /offers, the request is related to two passenger and is based on a tripSearchCriteria, containing
o Origin
o Destination
o departure time
• Post /bookings, the request is based on one of the offerId contained in the response of the Post /offers response.
• Post /bookings/{bookingId}/fulfillments, the request contains the bookingId produced by the previous interaction.
• Request of available refund offers with POST /bookings/{bookingId}/refund-offers related to one of the fulfillment obtained.
• Execute a refund based on one of the offers obtained, using PATCH /bookings/{bookingId}/refund-offers/{refundOfferId}.
Scenario

1. Generate and send a Post /offers request with a tripSearchCriteria, containing origin, destination and departure time, specify two passengers with anonymousPassengerSpecifications
2. Generate and send a Post /bookings request using one offer (identified by offerId) in the post offers response
3. Generate and send a Post /bookings/{bookingId}/fulfillments request using the booking id in the response of the post booking
4. Generate and send a POST /bookings/{bookingId}/refund-offers using the bookingId and one of the fulfillmentId (from the previous call), select a refundOfferId
5. Generate and send a PATCH /bookings/{bookingId}/refund-offers/{refundOfferId}, using in input the bookingId and the refundOfferId (from the previous API invocation response)

[TOP-PHE]

Put in priority 2 as the main priority is to deliver the scope of functionnalities on a 1 PAX_1 Leg type of offer first before managing more complex cases

[TOP-PHE]

Put in priority 2 as the main priority is to deliver the scope of functionnalities on a 1 PAX_1 Leg type of offer first before managing more complex cases