New features and bug fixes

Third Party API - Release v2025.21.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 21 May.

Third Party API

What's New

• A new POST endpoint has been added to compare all possible prices for a reservation proposal. The difference from the regular reservation proposal is that we share all options instead of returning only the cheapest option

  Endpoint POST /maxxton/v2/reservations/proposals/compare

What's Improved

• New parameters are added in the rentability stays endpoint

  The parameter minDuration and minArrival are added in the GET /maxxton/v2/rentability/stays endpoint

• The doorlocks endpoint is no longer returning reservations without a doorlock code. Also, now the doorlocks can be fetched for a date range of up to 30 days

  • GET /maxxton/v2/reservations/doorlocks

• Supported paymentOptions and instalments in the reservations proposal endpoint for multiple accommodations reservation

  It is now possible to retrieve paymentOptions and instalments when booking multiple accommodations via the POST /maxxton/v2/reservations/proposals endpoint

• New field is added in the add-ons endpoints

  The field applyDependencyMask is added to the following endpoints

  • GET /maxxton/v2/add-ons
  • GET /maxxton/v2/add-ons/{resourceId}

• New field is added in the reservations endpoints

  The field travelparty phoneNumber is added to the following endpoints

  • GET /maxxton/v2/reservations/{reservationId}/details
  • GET /maxxton/v2/reservations/details
  • GET /maxxton/v2/reservations/{reservationId}/subjects
  • GET /maxxton/v2/reservations/subjects
  • POST /maxxton/v2/reservations/{reservationId}/subjects
  • PUT /maxxton/v2/reservations/{reservationId}/subjects