Release note - v0.3388.0 ... v0.3389.0
- 3 new features
- 2 routes added
- 1 updated route
Highlights
- Enhanced services with transfer information (times, flight references, locations)
- New route to modify transfer information on a proposal
- New API resource to generate remote payment links (replacing the OGONE solution)
v0.3388.0 Details
Managing Transfers on Proposals
Two new features enhance transfer management in proposals:
Retrieving Transfer Information
The GET/v0/proposals/{proposal_id}/services route now returns a new transfer_information block in the schedules of transfer-type services. This block contains:
- The direction of the transfer (
way: INBOUND or OUTBOUND) - The customer's travel information (
customer_traveling_information), including time, flight reference, and transportation company - The departure (
from) and arrival (to) locations with their IDs and labels - An optional comment on the transfer
The transfer_information block is returned as null if no information is available in the source system or if all fields are empty.
Modifying Transfer Information
The new route PATCH/v0/proposals/{proposal_id}/transfers/{transfer_id} allows updating customer travel information for an existing transfer. This resource accepts the following changes per schedule:
- Flight time (
time) - Travel reference (
travel_reference) - Transportation company (
travel_company.id) - Comment on the transfer (
comment)
Unsent fields are not modified, while fields sent as an empty string are explicitly cleared. The route returns a 400 error if the transfer ID is invalid or if the provided schedules do not match the schedules of the existing transfer.
v0.3389.0 Details
Generating Remote Payment Links
The new route POST/v0/payments/link allows generating secure payment links for remote sales. This resource is accessible only with a PMS token and gradually replaces the OGONE solution scheduled for decommissioning.
The route accepts the following information as input:
- Customer and booking IDs (optional)
- Customer information (first name, last name, email)
- Phone number (required if the channel is SMS)
- Communication channel (EMAIL or SMS)
- Payment amount
- Link expiration date
- Club Med product ID
In response, the API returns:
- The payment link URL
- The HTTP method to use
- The ID of the generated payment
This solution ensures the continuity of VAD payment journeys for villages and customers.
Related routes
Lists the services a customer added to a proposal