DynpaX Book 3 - Changes and Updates
This document provides a short overview of changes that were made to the DynpaX Booking Service 3, the PHP client implementation and / or to this documentation.
Current PHP Reference implementation: v011
Changes since release v010
- Added tourOperatorName and tourOperatorCode to BookDescription
Changes since release v009
- Added optional, but preferred field 'birthdates' to the UnitOccupation object. To help select the correct unit options and offer a better packagePriceIndication.
- Deprecated paymentSchedule and invoice related fields. As Qenner no longer support an own Payment Service. The information in these fields can be disregarded and an own payment implementation and configuration should be maintained.
Please note, the packagePriceIndication now also includes the required costs to be paid locally.
Changes since release v008
- Update to Extra's, from and toDate are now deprecated and replaced by minStartDate, maxStartDate, minNightCount and maxNightCount. Those 4 values should should lead to a startDate and endDate assignment. if the min/maxStartDate items are ommited no date selection is required, if min/max nightCount is ommited no endDate selection is required.
- The BookingRequest has been extended with an preferredPackageCode item. If your DynpaXSearch/TravelSearch3 PriceDate object contains a packageCode then put it in this field for best search->book transfer.
- In the BookableUnitsResponse, the BookableAccommodation has been extended with package information as a PackageInfo. The PackageInfo object mirrors the object in the DynpaXSearch/TravelSearch3 current supported fields are:
{
"name": "Kos Stad/Imperial",
"code": "ACKOSIMPA",
"flags": ['IncludingTransfer']
}
- Extended UnitAssignmentDescription with packageInfo as well.
- Added stopovers to transport, if not null, contains the number of stopovers in flight. IMPORTANT: Transfer information, is currently minimally supported (JI, BF), info for the current assortment will be added the upcoming months. stopover, is minimally available for package-assortment. (F2)
Changes since release v007
- The service now support Train, Bus and Ferry Transport types. The flow is the same as for Flight trips, except for an additional optional PickupDropOff element.
- Transport not contains the property pickUpDropOffPoints with an optional list of PickupDropOffPoint objects, when such points are available a toPickupPoint and/or a fromDropoffPoint must be selected in the TransportAssignment.
- Transport has been extended with an departureLocation and arrivalLocation field, that can describe a location when the transport is none-flight.
- Transport and BookableUnit objects have been extended with an availabilityStatus field, indicating available, onrequest or unknown. This can help visualize whether selecting such a component may lead to an 'onrequest' booking.
- BookingDescription also has been extended with an availabilityStatus field, relevant after a getBookableExtra's and getPriceInfo, this can indicate what type of booking will be made. Note that after a completeBooking the status field represents the actual booking status.
Changes since release v006
- Extended the BookingSummary object with a list of BookingSummaryProviderReference objects in providerBookingReferences, containing information of all sub-bookings.
Changes since release v005
- Added optional contact / location information to BookedAccommodation / UnitAssignmentDescription
- Updated CancellationDetails
- Added support for Transfers
- Added getCompleteBookingResponse method to retrieve a previously created booking.
Changes since release v002
- A bug in the in the way how the Reference implementation sent the X-Test flag to the server.