Blog posts by Kathy Copeland

Blog posts by Kathy Copeland2026-06-18T15:05:21.0000000Zhttps://world.optimizely.com/blogs/kathy-copeland/ Optimizely World EOL Announcement for Preview3 CMS REST API<img src="https://statics.teams.cdn.office.net/evergreen-assets/personal-expressions/v2/assets/emoticons/stopsign/default/30_f.png?v=v6" alt="🛑" width="20" />Action Required: Migrate Preview3 API Integrations to CMS REST API v1 Before August 1, 2026 If your SaaS CMS applications are currently using the Preview3 CMS REST API endpoints, please plan to migrate to CMS REST API v1 before August 1, 2026. On August 1, 2026, we will retire the Preview3 endpoints and begin disabling access. Applications that continue to rely on Preview3 after this date may experience failed requests and service interruptions. <h3>Who Is Affected?</h3> You are affected by this change if your SaaS CMS integrations are currently making requests to Preview3 endpoints (typically URLs containing <code>/preview3/</code>). If your applications are already using CMS REST API v1, no action is required. We recognize that API migrations require planning and effort, and we appreciate the work our customers invest in keeping their integrations current. To help ensure a smooth transition, we've provided a migration guide (see below) and have maintained support for both versions since the release of v1 in May. This announcement is the first to underscore the importance of staying current and making the change to CMS REST API v1 to avoid disruption. <h2>What Is Changing?</h2> With the general availability of CMS REST API v1 on May 5, 2026, the Preview3 APIs entered a deprecation phase and are now approaching end-of-life. Key points to know: <ul> <li>Preview3 support ends August 1, 2026.</li> <li>Preview3 was released as an experimental API and was not recommended for production workloads.</li> <li>CMS REST API v1 provides the same core capabilities through stabilized, production-ready endpoints.</li> <li>Mixing Preview3 and v1 endpoints is supported until the August 1, 2026 retirement date.</li> <li>No new fixes, enhancements, or support updates are being made to Preview3. All ongoing investment is focused on v1 and future releases.</li> </ul> <h2>Will There Be Breaking Changes?</h2> Yes. Some breaking changes were introduced as part of the transition from Preview3 to v1. Before migrating, please review the migration documentation: <ul> <li><a class="fui-Link ___1q1shib f2hkw1w f3rmtva f1ewtqcl fyind8e f1k6fduh f1w7gpdv fk6fouc fjoy568 figsok6 f1s184ao f1mk8lai fnbmjn9 f1o700av f13mvf36 f1cmlufx f9n3di6 f1ids18y f1tx3yz7 f1deo86v f1eh06m1 f1iescvh fhgqx19 f1olyrje f1p93eir f1nev41a f1h8hb77 f1lqvz6u f10aw75t fsle3fq f17ae5zn" title="https://docs.developers.optimizely.com/content-management-system/v1.0.0-cms-saas/reference/migrate-content-api-preview3-to-v1" href="https://docs.developers.optimizely.com/content-management-system/v1.0.0-CMS-SaaS/reference/migrate-content-api-preview3-to-v1">Migrate from Content API Preview3 to CMS REST API v1</a></li> <li><a class="fui-Link ___1q1shib f2hkw1w f3rmtva f1ewtqcl fyind8e f1k6fduh f1w7gpdv fk6fouc fjoy568 figsok6 f1s184ao f1mk8lai fnbmjn9 f1o700av f13mvf36 f1cmlufx f9n3di6 f1ids18y f1tx3yz7 f1deo86v f1eh06m1 f1iescvh fhgqx19 f1olyrje f1p93eir f1nev41a f1h8hb77 f1lqvz6u f10aw75t fsle3fq f17ae5zn" title="https://docs.developers.optimizely.com/content-management-system/v1.0.0-cms-saas/reference/experimental-apis" href="https://docs.developers.optimizely.com/content-management-system/v1.0.0-CMS-SaaS/reference/experimental-apis">Experimental APIs Documentation</a></li> </ul> These resources provide detailed guidance on the changes and recommended migration approach. <h2><img src="https://statics.teams.cdn.office.net/evergreen-assets/personal-expressions/v2/assets/emoticons/1f552_threeoclock/default/30_f.png?v=v13" alt="🕒" width="20" />Why Are We Retiring Preview3?</h2> Maintaining multiple API versions increases complexity for both customers and Optimizely. As v1 has been generally available for several months and provides a stable, supported alternative, retiring Preview3 allows us to focus on delivering higher reliability, better performance, and faster innovation across the platform. <h2><img src="https://statics.teams.cdn.office.net/evergreen-assets/personal-expressions/v2/assets/emoticons/1f4e2_publicaddressloudspeaker/default/30_f.png?v=v8" alt="📢" width="20" />How Can I Stay Informed?</h2> We recommend subscribing to the following channels for future API lifecycle and platform updates: <ul> <li>CMS Release Notes (support.optimizely.com)</li> <li>Optimizely Slack Community</li> <li>Optimizely Developer Blog Community (World.optimizely.com)</li> </ul> These channels are typically the first places where deprecations, support timelines, and migration guidance are communicated. For additional information about API lifecycle and support policies, please refer to the <a class="fui-Link ___1q1shib f2hkw1w f3rmtva f1ewtqcl fyind8e f1k6fduh f1w7gpdv fk6fouc fjoy568 figsok6 f1s184ao f1mk8lai fnbmjn9 f1o700av f13mvf36 f1cmlufx f9n3di6 f1ids18y f1tx3yz7 f1deo86v f1eh06m1 f1iescvh fhgqx19 f1olyrje f1p93eir f1nev41a f1h8hb77 f1lqvz6u f10aw75t fsle3fq f17ae5zn" title="https://docs.developers.optimizely.com/content-management-system/v1.0.0-cms-saas/reference/experimental-apis" href="https://docs.developers.optimizely.com/content-management-system/v1.0.0-CMS-SaaS/reference/experimental-apis">CMS API documentation</a>. <h2>Thank You</h2> Thank you for your partnership and for helping us continue to improve the CMS developer experience. If you have questions about your migration strategy or encounter challenges during the transition, please reach out to our team—we're here to help.2026-06-18T15:05:21.0000000Z

Blog post

📣 Build, Automate, and Scale Content Operations with CMS REST API v1 - now live! Now available for both CMS13 and CMS SaaS We are excited to announce the v1 release of our CMS REST API—a major milestone in delivering a stable, production-ready foundation for automating and integrating with Optimizely’s CMS. This release will apply to both our recently released CMS13 on PaaS and our CMS SaaS platforms. 💡 Why this matters  Previous iterations of our CMS REST API were released as preview versions allowing us to make available these short term stable releases as we continue to mature the API. With v1, we are officially shifting to a commitment of stability, backward compatibility, and long-term support—providing our developer audience and partners the confidence to build their integrations with our CMS platforms at scale.  This release aligns closely with the capabilities of the Optimizely SaaS CMS UI, ensuring consistency between what users see and what developers can programmatically control. For CMS13 developers, only those features available in the CMS13 user experience will be covered by the CMS REST API.  An overview of migrating from Preview3 to v1 for the CMS REST API for SaaS can be found <a class="fui-Link ___1q1shib f2hkw1w f3rmtva f1ewtqcl fyind8e f1k6fduh f1w7gpdv fk6fouc fjoy568 figsok6 f1s184ao f1mk8lai fnbmjn9 f1o700av f13mvf36 f1cmlufx f9n3di6 f1ids18y f1tx3yz7 f1deo86v f1eh06m1 f1iescvh fhgqx19 f1olyrje f1p93eir f1nev41a f1h8hb77 f1lqvz6u f10aw75t fsle3fq f17ae5zn" title="https://docs.developers.optimizely.com/content-management-system/v1.0.0-cms-saas/reference/migrate-content-api-preview3-to-v1" href="https://docs.developers.optimizely.com/content-management-system/v1.0.0-CMS-SaaS/reference/migrate-content-api-preview3-to-v1">here</a>:  Documentation for the CMS REST API v1 for CMS13 can be found <a class="fui-Link ___1q1shib f2hkw1w f3rmtva f1ewtqcl fyind8e f1k6fduh f1w7gpdv fk6fouc fjoy568 figsok6 f1s184ao f1mk8lai fnbmjn9 f1o700av f13mvf36 f1cmlufx f9n3di6 f1ids18y f1tx3yz7 f1deo86v f1eh06m1 f1iescvh fhgqx19 f1olyrje f1p93eir f1nev41a f1h8hb77 f1lqvz6u f10aw75t fsle3fq f17ae5zn" title="https://docs.developers.optimizely.com/content-management-system/v13.0.0-cms/reference/introduction-cms-rest-api" href="https://docs.developers.optimizely.com/content-management-system/v13.0.0-CMS/reference/introduction-cms-rest-api">here</a>:  <h2>🆕 What’s Included in v1?</h2> The v1 API delivers a comprehensive set of endpoints designed to support the full content lifecycle and schema management of the CMS platform programmatically. Any developers who have been using Preview3 endpoints will be familiar with many of the v1 endpoints. New to V1 are the following: <ul> <li>Content: Manage content and versions (moved out of experimental status) <ul> <li>Standalone content lifecycle endpoints (new)</li> </ul> </li> <li>Content Types: Define structured schemas for pages, blocks for programmatic content modeling</li> <li>Content Sources: Create and manage external content sources (new)</li> <li>Content Type Bindings: Map relationships and property associations for external content sources (new)</li> <li>Blueprints: Create and manage content blueprints</li> <li>Locales: Manage supported content languages (new)</li> <li>Display templates: Create and manage style display templates for use in the CMS visual builder.</li> <li>Property groups: Create and manage content property groups.</li> <li>Manifest: Export and/or import a content manifest with content types, locales, display templates and property groups</li> <li>Credentials: Manage client credentials for secure API access (SaaS only)</li> </ul> The Packaging API remains under the /experimental/ prefix in v1. For more information about our policy regarding Experimental endpoints, please refer to the documentation found <a class="fui-Link ___1q1shib f2hkw1w f3rmtva f1ewtqcl fyind8e f1k6fduh f1w7gpdv fk6fouc fjoy568 figsok6 f1s184ao f1mk8lai fnbmjn9 f1o700av f13mvf36 f1cmlufx f9n3di6 f1ids18y f1tx3yz7 f1deo86v f1eh06m1 f1iescvh fhgqx19 f1olyrje f1p93eir f1nev41a f1h8hb77 f1lqvz6u f10aw75t fsle3fq f17ae5zn" title="https://docs.developers.optimizely.com/content-management-system/v1.0.0-cms-saas/reference/experimental-apis" href="https://docs.developers.optimizely.com/content-management-system/v1.0.0-CMS-SaaS/reference/experimental-apis">here</a>. Now, with the v1 CMS REST API, developers and development partners can depend upon Optimizely CMS API stability and continuity between SaaS and PaaS releases. Further, they will be able to trust the enterprise readiness, security, and performance of their applications at scale. This transition offers our developer audience the confidence they need to take the Optimizely CMS platform to scalable content operations beyond just our user interfaces. V1 is just the start of big things to come! 🚀2026-04-21T21:47:48.0000000Z

Blog post