The v2 API is created to give you programmatic access to all your objects in Optimizely X. You can use the v2 API to read Optimizely Classic data, but to write to Optimizely Classic you will have to use the v1 API. Full Stack, Mobile, and OTT are not currently supported.
The v2 API is designed to give easy access to all the resources in your Optimizely X projects through a REST interface. Our API is designed to mirror the functionality of the Optimizely UI as close as possible. To do so, the endpoints have predictable, resource-oriented URLs. All the endpoints are defined using the OpenAPI Specification. With the OpenAPI Specification we guarantee that the documentation below is always up to date and that it is easy to create API clients in any programming language using the Swagger Generator. It is also possible to use any off-the-shelf HTTP client to make requests directly. The API returns JSON in the body of responses.
The preferred method of authenticating with the API is using OAuth 2.0, but to make our API easily explorable we have implemented Personal tokens. Personal tokens have replaced the tokens used by our v1 API.
If there is no value set for a field (the value is undefined) the field will not appear in the JSON response.
We have documented the most important API conventions:
- Rate limiting
- Reading Optimizely Classic objects
- The OpenAPI Specification
- Required fields
Looking for endpoints for DCP (Dynamic Customer Profiles)?