How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Optimizely

Optimizely Flags Scheduling API

Schedule future flag ruleset changes and read environment change-approval settings. Five operations. Harvested verbatim from the provider's published OpenAPI 2026-08-13.

Documentation Provider Profile APIs.io OpenAPI GitHub

Optimizely Flags Scheduling API 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 Scheduling. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 5 operations across 3 paths, organized into 3 resource areas, and defines 20 schemas. It is described by OpenAPI 3.0.0, at version 1.0.0.

Requests are made against 2 base URLs: http://localhost:3002/, https://api.app.optimizely.com/flags-scheduling.

5 operations 3 paths 20 schemas 1 DELETE2 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
1.0.0
Base URL
https://api.app.optimizely.com/flags-scheduling
Authentication
HTTP Bearer
Resource Areas
3

Authentication & Security 1

Optimizely Flags Scheduling API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (BearerAuth).

  • BearerAuth — To get a personal token, see https://docs.developers.optimizely.com/web/docs/personal-token

Paths & Operations 5

Across 3 paths, the API surfaces 5 operations — 1 DELETE, 2 GET, 1 PATCH, 1 POST. They span 3 resource areas: Change Approvals, Scheduled Changes, Scheduled Change. Each is listed below with its method, path, parameters, and response codes.

Change Approvals 1

APIs to interact with approval of flag changes

GET
/projects/{project_id}/environments/{environment_id}/preferences
get_environment_approval_settings 2 params → 200401422
Scheduled Changes 2

APIs to interact with Scheduled Change of a flag

GET
/projects/{project_id}/flags/{flag_key}/schedules
List Scheduled changes of a flag
list_scheduled_changes 9 params → 200401422
POST
/projects/{project_id}/flags/{flag_key}/schedules
Create a Schedule Change for a flag in an environment
create_scheduled_change 2 params body → 201401422
Scheduled Change 2

APIs to interact with Scheduled Change of a flag in an environment

DELETE
/projects/{project_id}/flags/{flag_key}/schedules/{schedule_id}
Delete a Scheduled Change for a flag in an environment
delete_scheduled_change 3 params → 204400401422
PATCH
/projects/{project_id}/flags/{flag_key}/schedules/{schedule_id}
Update the Scheduled Change for a flag in an environment
update_scheduled_change 3 params body → 200401404422

Schemas 20

The contract defines 20 schemas that model the data the API accepts and returns. The most detailed are ScheduledChange (13 properties), EnvironmentApprovalSettingsResponse (11 properties), EntityApprovalSettingsResponse (8 properties), EnvironmentApprovalSettingsUpdate (7 properties). Each schema is shown below with its type and property counts.

ErrorResponse
object
2 properties 2 required
HTTPValidationError
object
2 properties
PaginatedSchedulesResponse
object
3 properties 3 required
ScheduledTime
object
3 properties 3 required
EnvironmentApprovalSettings
object
6 properties 5 required
EntityApprovalSettings
object
4 properties 3 required
EntityApprovalSettingsCreate
object
4 properties 3 required
EntityApprovalSettingsResponse
object
8 properties 5 required
EnvironmentApprovalSettingsCreate
object
6 properties 5 required
EnvironmentApprovalSettingsResponse
object
11 properties 10 required
ApproversResponse
object
2 properties 2 required
EnvironmentApprovalSettingsUpdate
object
7 properties 5 required
ScheduledTimeWithUTC
object
4 properties 4 required
ScheduleAction
object
3 properties 3 required
ScheduledChangeCreateRequest
object
4 properties 4 required
ScheduledChangeUpdateRequest
object
3 properties
ScheduledChange
object
13 properties 13 required
ValidationError
object
3 properties 3 required
ActionValue
The value of a schedule action. For status change, value can be on/off. For changing traffic percentage, value should be integer. For example, for 40% traffic,…
SortOrder
string

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

optimizely-feature-experimentation-optimizely-flags-scheduling-api-openapi.json Raw ↑

Other APIs Optimizely publishes across the network.

Optimizely Experimentation REST API v2
AE Profile APIs.io
Optimizely Feature Experimentation Flags API v1
AE Profile APIs.io
Optimizely Permission Service API
AE Profile APIs.io
Optimizely Agent API
AE Profile APIs.io
Optimizely Event API
AE Profile APIs.io
Optimizely Edge Decider API
AE Profile APIs.io
Optimizely Data Platform (ODP) API v3
AE Profile APIs.io
Optimizely Graph API
AE Profile APIs.io
Optimizely Content Marketing Platform (CMP) API v3
AE Profile APIs.io
Optimizely Campaign REST API
AE Profile APIs.io
Optimizely Configured Commerce API
AE Profile APIs.io
Optimizely CMS Content Delivery API v3.0
AE Profile APIs.io
#Feature Flags#Scheduling
← Back to O APIs
API Details
ID
optimizely:flags-scheduling-api
Base URL
https://api.app.optimizely.com/flags-scheduling
Docs
https://docs.developers.optimizely.com/feature-experimentation/reference
Provider
Optimizely
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

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.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=flags-scheduling-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/flags-scheduling-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

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 Flags Scheduling API, 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.