New features and bug fixes

Third Party API - Release v2025.3.0

Your Third Party API experience is improving as we work to squash bugs and release new features. Here's an account of the improvements you'll find in the latest releases.

This release is now available on production at 15 January.

Third Party API

What's New

• New GET endpoints are added to fetch distribution channels details

  Endpoints GET maxxton/v1/distributionchannels/details and GET maxxton/v1/distributionchannels/{distributionChannelId}/details

• New PUT endpoints are added to update the customer status

  Endpoint PUT /maxxton/v1/customers/{customerId}/customerstatus is added to update the customer status

• New POST endpoint is added to create reservation proposal for existing reservation

  Endpoint POST /maxxton/v1/reservations/{reservationId}/proposals is added to check possibilities and impact of changing an existing reservation

What's Improved

• New fields are added in the financialtransaction journal reports endpoint

  Following fields are added in the endpoint GET /maxxton/v1/adminorganisations/{adminOrganisationId}/financialtransactions/{financialTransactionReportId}/journals

  • reservationNumber
  • pspReferenceNumber

• Supported required travel party details in the resort endpoints

  The required travel party details are added in the following endpoints

  • GET /maxxton/v1/resorts/details
  • GET /maxxton/v1/resorts/{resortId}/details
  • GET /maxxton/v1/resorts/{resortId}/subjects

• The Reservation endpoints now support both offerCode and voucherCode simultaneously

  Both offerCode and voucherCode are now supported in the POST /maxxton/v1/reservations/proposals and POST /maxxton/v1/reservations endpoints to be used at the same time

• New fields are added in the reservation doorlock endpoint

  Following fields are added in the endpoints GET /maxxton/v1/reservations/doorlocks and GET /maxxton/v1/reservations/{reservationId}/doorlocks endpoints

  • doorlockType
  • lockCode
  • bluetoothLowEnergy