Overview

The preferential access strategy in Izix involves automatic daily bookings for up to 90 days, ensuring users are guaranteed spots. While this system is convenient and guarantees availability, it can lead to situations where capacity is allocated but remains unused. To address this, Izix provides release endpoints that allow clients to automate the release of preferential reservations. This is especially useful for clients who track vacations and absences internally and wish to avoid relying on users to manually release reservations.

Usage Notes

Automated Release Mechanism

• Method: Clients with internal tracking systems for vacations and absences can integrate with Izix release endpoints to automatically manage the release of reservations when they are not needed.
• Cancellation of Releases: If a release is no longer necessary, it can be cancelled through the delete endpoint. This action will restore the previously reserved capacity.

Managing Dual Updates

• Challenge: When users actively engage with the Izix platform and can register their own releases, there may be conflicts regarding which system is the source of truth.
• Recommendation: Use the reason parameter to distinguish releases initiated by your system from those made by users directly on the Izix platform. This helps maintain clear and traceable records of why and by whom a reservation was released.

Key Attributes

• valid_from: The datetime from which the release should begin. This marks the start of the period during which reservations are not needed.
• valid_to: The datetime when the release should end, inclusive. This indicates the date and time after which the reservations needs can resume.
• reason: A description of why the release is occurring. This attribute is crucial for tracking and managing releases, especially in environments where multiple systems or users may initiate releases.