Shift-Based Schedules: Upgrading to the V3 Shift Schedules API

The V3 Shift Schedules API replaces the legacy V2 Layers logic with a redesigned, shift-based architecture. This upgrade allows internal tooling and automations management with the same precision as modern calendar standards (iCal). By moving away from the complexity of the old layers-based schedules, the V3 API provides exact control over rotations, supporting multi-responder shifts, automated recurring patterns, and "shadow rotations" for seamless onboarding. Upgrading ensures internal tools can leverage these granular controls, providing a more reliable and scalable foundation for teams’ on-call logic.

Implementation & Compatibility

To maintain service continuity while you adopt these new features, please note the following:

• API Specificity: Shift-based schedules are exclusive to the V3 API; therefore, internal automations must be upgraded to V3 to interact with new shift-based configurations.
• Coexistence: Existing legacy schedules will continue to function via the V2 endpoints. We recommend a hybrid approach; use V3 for all new schedules while maintaining V2 for your historical data.
• Upgrade Path: V2 schedules will remain fully supported and operational. An automated tool to help transition legacy schedules to the new format is currently in development.

📘

Developer Resources

Explore our developer resources or V3 endpoint schema definitions and integration examples.