Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

New features and bug fixes

Third Party API - Release v2024.45.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 acceptance at 31 October and will (probably) be released to production on 6 November or on 12 November in case of unforeseen test results.

Note 
This release note for the test environment is indicative of the possible features to be released in the production environment. In case one or more feature(s) are unstable or have bugs/issues, the feature(s) would not be a part of the production release. Kindly also check the linked tickets for more information.

Third Party API

What's Improved

  • The reservation proposal call supports multiple additions in case of multiple accommodation types

    Duplicate additions are allowed for both accommodation types if they share common elements, but they must have different resource IDs.

  • New field is added in the unit workorders endpoint

    The field referenceNumber added in the Endpoint GET /maxxton/v1/units/workorders

  • New field is added in the owners endpoint

    The field birthCountryId added in the Endpoint GET /maxxton/v1/owners and GET /maxxton/v1/owners/{ownerid}

  • New field is added in the reservations payments endpoint

    The field paymentMethod added in the Endpoint GET /maxxton/v1/reservations/payments and GET /maxxton/v1/reservations/{reservationId}/payments

What's New

  • A New GET endpoint is added to retrieve customer status categories

    Endpoint GET /maxxton/v1/customerstatus/categories


  • No labels