As part of our ongoing commitment to security, reliability, and platform modernisation, the legacy Space Scheduling API used in version 1.18 and earlier will be retired on 31 December 2026.

This API was superseded in version 1.19 by our modern multi-tenant API platform, which provides a more secure and scalable foundation for future enhancements.

Why is this change being made?

The legacy API is being retired because the replacement API provides improved security, supportability, and long-term platform sustainability.

What does this mean for you?

If you are currently using the legacy API for integrations with Space Scheduling, you will need to migrate to the current API before 31 December 2026.

Failure to migrate before this date may result in your integrations ceasing to function once the legacy API is decommissioned.

Next Steps

If you believe you may be using the legacy API, or if you are unsure which API version your integration uses, please contact your Customer Success Manager or MRI Support as soon as possible. Our team can help you assess your current implementation and provide guidance on the migration process.

We have communicated the transition to the modern API since the release of version 1.19, and many customers have already completed their migration. We encourage any remaining customers to begin planning their migration activities to ensure a smooth transition well ahead of the retirement date.

Thank you for your continued partnership and support.

Kind regards,

Graham Croker
Senior Product Manager IV