Capacity – API Compatibility When Migrating from Time Slots to Booking Intervals

Summary:

Currently, the Capacity model based on Time Slots (AM/PM booking slots) is being used.

The following APIs are used to retrieve booking options:

• REST: /rest/ofscCapacity/v1/activityBookingOptions
• SOAP: /soap/capacity/?wsdl

A migration from the current model to Booking Intervals (Availability-Based Quota) is being considered.

Our question is: Is it mandatory to migrate to the REST API showBookingGrid when using Booking Intervals, or is it possible to continue using the existing APIs (activityBookingOptions and SOAP Capacity)?

If the existing APIs can be retained, are there any functional limitations or considerations we should be aware of?

We would appreciate any feedback, recommendations, or experience with this scenario.