About the Feature Experimentation APIs

Optimizely Feature Experimentation has multiple REST APIs you can use to do administrative tasks on your Feature Experimentation project. The following describes the functionality of the available REST APIs and what endpoints are available for Optimizely Feature Experimentation.

For the most common operations in an experiment's lifecycle using the Optimizely APIs, see the Feature Experimentation REST API Cookbook, which is hosted on GitHub.

For information on generating API keys, see Generate tokens and use the REST APIsGenerate tokens and use the REST APIs. See Find IDs for API callsFind IDs for API calls for specific IDs required for certain API endpoints.

The Optimizely Feature Experimentation API has a rate limit of two requests per second, 120 requests per minute.

You can use the Optimizely Feature Experimentation APIOptimizely Feature Experimentation API to manage the following items:

Use the Optimizely APIOptimizely API for additional management that the Optimizely Feature Experimentation API does not cover. You can use the Optimizely API for other types of Experimentation projects, such as Web ExperimentationWeb Experimentation and Full Stack (Legacy)Full Stack (Legacy).

The Optimizely API has a rate limit of 100 requests per minute. The Get Campaign resultsGet Campaign results and Get Experiment resultsGet Experiment results endpoints have a rate limit of 20 requests per minute.

The following Optimizely API endpoints are available in Optimizely Feature Experimentation:

Use the Scheduling API to list, create, update, or delete scheduled changesscheduled changes for your flags and rules.

Use the Permission Service APIPermission Service API to get and update user permissions.

The Optimizely Agent APIOptimizely Agent API manages your Optimizely Feature Experimentation AgentAgent instance.