Versions Compared

Old Version 1

changes.mady.by.user Serveruser Maxxton

Saved on

compared with

New Version Current

changes.mady.by.user Serveruser Maxxton

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

New features and bug fixes

Third Party API - Release v2024.19.0

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.

acceptance at 3 May and will (probably) be released to production on 8 May or on 14 May in case of unforeseen test results.

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 14 May.

GET update reservation

What's Improved

Custom fields information added in the response of reservations endpoints

returnSections=CUSTOMFIELDS supported in the GET /details GET /maxxton/v1/reservations/{reservationId}/details

Third Party API

What's New

  • A New

  • POST endpoint is added to

  • add custom fields to the reservations

    Endpoint POST /maxxton/v1/reservations/{reservationId}/reservedresources/{reservedResourceId}/customfields

  • A New GET endpoint is added to fetch applicable custom fields for the reservation

    Endpoint GET maxxton/v1/reservations/

  • {reservationId}/reservedresources/{reservedResourceId}/customfields

What's Improved

  • Added CUSTOMER_EVENT if loyalty points and customer status is updated

    Endpoint GET /maxxton/v1/events

Show all tickets included in this release