Information on experimentation APIs in Content Management System (CMS) (SaaS).
Experimental APIs are features or functionalities that are in the early stages of development. They are not ready for general use and may change significantly or be removed in future updates. They are provided to let you test and provide feedback before the APIs are finalized.
How do I get access?
Sign up for specific betas that interest you on Optimizely.com to get a sneak peek at experimental features designed to optimize your digital experiences and help shape the next generation of Optimizely.
What to expect from such APIs?
Experimental APIs come with the following expectations:
- They might not be fully stable. There may be frequent updates, changes to functionality, or even breaking changes without prior notice.
- They may not have all the features you would expect from a mature API. Some endpoints might be incomplete.
- They are subject to change or removal as developers incorporate feedback and add support for additional scenarios.
- They can be temporarily or permanently removed.
Do not use experiment APIs in production environments
While testing the experimental APIs is a way to get experience with them before most other developers, you should not use them in production environments. These APIs are unstable, subject to breaking changes without notice, and may be removed entirely.