Optimizely Feature Experimentation Flags API v1 is one of 50 APIs that Optimizely publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Feature Flags and Experimentation. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.
This API exposes
55 operations
across 37 paths,
organized into 11 resource areas,
and defines 68 schemas.
It is described by OpenAPI 3.0.0, at version 0.3.7.
Requests are made against a single base URL, https://api.optimizely.com/flags/v1/.
55 operations37 paths68 schemas6 DELETE21 GET6 PATCH22 POST
Metadata
The identity and technical contract details declared by the specification.
Specification
OpenAPI 3.0.0
API Version
0.3.7
Base URL
https://api.optimizely.com/flags/v1
Authentication
HTTP Bearer, OAuth 2.0, HTTP Bearer
Resource Areas
11
Authentication & Security 3
Optimizely Feature Experimentation Flags API v1 declares
3 security schemes
for authenticating requests.
It accepts HTTP bearer tokens (BearerAuth).
It supports OAuth 2.0 (OAuth2) using the authorizationCode flow, exposing 1 scope.
It accepts HTTP bearer tokens (apiKey).
By default, every request must be authenticated.
BearerAuth — To get a personal token, see https://docs.developers.optimizely.com/web/docs/personal-token
OAuth2 — Write applications that authenticate with the REST API via OAuth 2.0.
Paths & Operations 55
Across 37 paths, the API surfaces 55 operations — 6 DELETE, 21 GET, 6 PATCH, 22 POST. They span 11 resource areas, including Custom Fields, Environments, Reports, Rules, Flags, Changes, Rulesets, Variable Definitions, and 3 more. Each is listed below with its method, path, parameters, and response codes.
Custom Fields 5
APIs to manage Custom Field definitions for organizing and annotating flags
The contract defines 68 schemas that model the data the API accepts and returns. The most detailed are Rule (34 properties), RulesetRule (31 properties), Report (30 properties), Flag (24 properties). Each schema is shown below with its type and property counts.
AudienceConditions
An Audience Combination composed of other audiences. Each audience is a rule like 'User likes salads', and an Audience Combination is a Boolean combination of…
AudienceConditionsArray
array
AudienceConditionsString
string
A valid AudienceConditionsArray represented as a JSON string
BrainstormError
object
3 properties3 required
BrainstormUserChat
object
3 properties2 required
BrainstormVariableDefinition
object
4 properties4 required
BrainstormVariablesChat
object
1 property1 required
BrainstormVariablesInteraction
object
BrainstormVariablesResponse
object
3 properties3 required
BrainstormVariation
object
4 properties4 required
BrainstormVariationsChat
object
1 property1 required
BrainstormVariationsInteraction
object
BrainstormVariationsResponse
object
3 properties3 required
BulkOperationsRequestBody
object
1 property
ChangeHistory
array
Environment
object
9 properties5 required
EnvironmentMap
object
Map of environments that include environment key as key and environment payload as value.
Environments
object
12 properties8 required
EventPropertyCondition
object
4 properties4 required
Flag
object
24 properties8 required
FlagEnvironment
object
12 properties3 required
FlagMap
object
Map of flags that include flag key as key and flag payload as value.
FlagRequestBody
object
7 properties1 required
Flags
object
15 properties8 required
CustomField
object
15 properties6 required
CustomFieldRequestBody
object
6 properties4 required
CustomFieldUpdateRequestBody
object
3 properties
CustomFieldsList
object
10 properties8 required
Group
object
17 properties6 required
GroupMap
object
Map of groups that include group id as key and group payload as value.
GroupRequestBody
object
4 properties2 required
GroupRule
object
8 properties1 required
GroupRuleMap
object
Map of group rules that include rule id as key and group rule as value.
Groups
object
14 properties8 required
Holdout
object
Represents a holdout experiment that reserves a portion of traffic to measure the impact of feature flags and experiments. Holdouts help establish control grou…
22 properties3 required
HoldoutExperiment
object
Represents a single experiment rule that is connected to a holdout configuration. Contains experiment identification, timing information from the associated re…
4 properties1 required
HoldoutExperiments
array
A collection of experiment rules associated with a holdout. Each item represents an experiment that is connected to the holdout through database relationships…
HoldoutMap
object
A dictionary/map of holdouts where each key is the holdout ID and the value is the holdout object. This structure is used internally for efficient lookups and…
HoldoutRequestBody
object
Request body schema for creating or updating a holdout. Holdouts are experiments that reserve a portion of your traffic to measure the impact of your feature f…
20 properties2 required
HoldoutsList
array
A simple array of holdout objects without pagination metadata. Used by endpoints that return a basic list of holdouts, such as when fetching holdouts associate…
HoldoutsPaginatedList
object
Paginated response structure for holdout collections with navigation links and metadata. This response format follows the standard pagination pattern used acro…
12 properties8 required
Metric
object
13 properties2 required
PatchRequestBody
object
A JSONPatch document as defined by RFC 6902
4 properties2 required
ProblemDetail
object
https://tools.ietf.org/html/rfc7807section-3.1
5 properties4 required
Report
object
Report with results for the active rule for a flag in a project.
30 properties10 required
ReportMap
object
Map of reports that include report key as key and report payload as value.
Reports
object
Summary of the Reports for Flags in a project
14 properties8 required
Rule
object
Configuration which contains audiences, metrics and variations.
34 properties3 required
RuleAllowList
object
2 properties2 required
RuleDetails
object
17 properties7 required
RuleGroupRule
object
3 properties1 required
RuleMap
object
RuleVariation
object
6 properties1 required
Rules
object
6 properties6 required
Ruleset
object
Rules configuration specific to an environment.
22 properties5 required
RulesetRule
object
Configuration which contains audiences, metrics and variations.
31 properties3 required
RulesetRuleVariation
object
5 properties1 required
RulesetSummary
object
1 property
SubMetric
object
6 properties
UrlList
array
A list of urls.
UrlValue
string
A single url.
VariableDefinition
object
6 properties3 required
VariableDefinitions
object
9 properties
VariableValue
object
5 properties1 required
Variation
object
21 properties8 required
VariationMap
object
Map of variations that include variation key as key and variation payload as value.
VariationRequestBody
object
4 properties2 required
Variations
object
15 properties8 required
Specification
The full machine-readable OpenAPI contract behind this narrative.
Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.
Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.
MCP tools for apis
4 tools reach this content
search_api_evangelistSearch every content type across the network at once.
find_relatedThe shared-tag relevance graph — what else covers this.
get_tagEverything one tag labels, across all content types.
guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
A second provider on the same verified email joins the account you already have.
Your account
ⓘWhere this information came from
This is an independent, third-party profile of Optimizely Feature Experimentation Flags API v1, published by
API Evangelist. We do not operate, host, resell, or
support these APIs, and we are not affiliated with or endorsed by the company unless stated above.
Everything here is built from publicly available information — the company's own site,
developer portal, documentation, public repositories, and the specifications it publishes for public use.
Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's
public API artifacts, scored against a published rubric. They are not certifications,
endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and
you do not need to justify the request. A removed company is recorded as unrated, never scored
zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy → On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.
