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

Optimizely πŸ“– Definition ( v3 ) API

The πŸ“– Definition ( v3 ) API from Optimizely β€” 2 operation(s) for πŸ“– definition ( v3 ).

Optimizely πŸ“– Definition ( v3 ) API is one of 420 APIs that Optimizely publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include πŸ“– Definition ( v3 ). The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 6 operations across 2 paths, and defines 17 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 2 base URLs: https://cg.optimizely.com, https://prod.cg.optimizely.com.

6 operations 2 paths 17 schemas 1 DELETE2 GET2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://exp.mcp.opal.optimizely.com/mcp
Authentication
API Key, API Key, HTTP Basic, HTTP Bearer
License
Resource Areas
1

Authentication & Security 4

Optimizely πŸ“– Definition ( v3 ) API declares 4 security schemes for authenticating requests. An API key is passed in the query as auth (epi-single). An API key is passed in the header as Authorization (epi-hmac). It accepts HTTP basic authentication (Basic). It accepts HTTP bearer tokens (JWT) (Bearer).

  • epi-single β€” Single key authentication
  • epi-hmac β€” HMAC authentication (epi-hmac xxx)
  • Basic β€” HMAC credentials
  • Bearer β€” JWT token

Paths & Operations 6

Across 2 paths, the API surfaces 6 operations β€” 1 DELETE, 2 GET, 2 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

πŸ“– Definition ( v3 ) 6
GET
/api/content/v3/sources
Get source metadata
get-ContentV3SourceHandler 2 params → 200
DELETE
/api/content/v3/sources
Delete source
delete-ContentV3SourceHandler 3 params → 200404
POST
/api/content/v3/sources
Update source metadata
post-ContentV3SourceHandler 2 params body → 204
GET
/api/content/v3/types
Get content types
get-ContentV3TypeHandler 1 param → 200
POST
/api/content/v3/types
Partial content type update
post-ContentV3TypeHandler 1 param body → 204
PUT
/api/content/v3/types
Full content type update
put-ContentV3TypeHandler 1 param body → 204

Schemas 17

The contract defines 17 schemas that model the data the API accepts and returns. The most detailed are ContentSource_V3 (8 properties), ContentType_V3 (7 properties), ContentTypeProperty_V3 (5 properties), SourceInfo (4 properties). Each schema is shown below with its type and property counts.

Slot
string
PropertyType_V3
object
3 properties
ContentType_V3
object
7 properties 1 required
DeleteMode
string
LinkMap
object
Optional_string_
stringnull
SourceInfo
object
4 properties 4 required
Property_V3
object
4 properties 1 required
SourceInfoMap
object
ContentTypeMap_V3
object
ContentSource_V3
object
8 properties
PropertyTypeMap_V3
object
LinkConfig
object
2 properties 2 required
FieldRef
object
2 properties
ContentTypeProperty_V3
object
5 properties 1 required
Preset
string
SourceMetadata
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

optimizely-definition-v3-api-openapi.yml Raw ↑

Other APIs Optimizely publishes across the network.

Optimizely Remote MCP Server β€” Experimentation
Optimizely Assets API
Optimizely Attributes API
Optimizely Audiences API
Optimizely Campaigns API
Optimizely Catalog Entries API
Optimizely Catalog Entry Relations API
Optimizely Catalog Nodes API
Optimizely Catalogs API
Optimizely Content API
Optimizely Content Types API
Optimizely Customers API
Where this information came from

This is an independent, third-party profile of Optimizely πŸ“– Definition ( v3 ) 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.