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 CMS Content Delivery API v3.0

Read-only content delivery from Optimizely CMS — content by identifier, children, ancestors, and site metadata. Deployed inside the customer's own CMS instance, so the base URL is the customer's CMS host. One of only two Optimizely documents that use RFC 9457 problem+json. Harvested verbatim 2026-08-13.

Optimizely CMS Content Delivery API v3.0 is one of 50 APIs that Optimizely publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Content Management and Headless. The published artifact set on APIs.io includes an OpenAPI specification and an API reference.

This API exposes 6 operations across 6 paths, organized into 2 resource areas, and defines 7 schemas. It is described by OpenAPI 3.0.1, at version v3.

Requests are made against the base URL https://{cms-host}/api/episerver/v3.0.

6 operations 6 paths 7 schemas 6 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
v3
Base URL
https://{cms-host}/api/episerver/v3.0
Resource Areas
2

Paths & Operations 6

Across 6 paths, the API surfaces 6 operations — 6 GET. They span 2 resource areas: Content, Site. Each is listed below with its method, path, parameters, and response codes.

Content 4
GET
/api/episerver/v3.0/content/{contentIdentifier}
Get content by given content reference or unique identifier and language.
Content_GetByContentIdentifier 4 params → 200400403404
GET
/api/episerver/v3.0/content/{contentIdentifier}/children
Get the children of the content item by given content reference or unique identifier and language.
Content_GetChildren 6 params → 200400403404
GET
/api/episerver/v3.0/content/{contentIdentifier}/ancestors
Get the ancestors of the content item by given content reference or unique identifier and language.
Content_GetAncestors 4 params → 200400403404
GET
/api/episerver/v3.0/content
Get content by given content url or by list of GUID/Reference with given language
Content_QueryContent 7 params → 200400403404
Site 2
GET
/api/episerver/v3.0/site
Get a list of sites.
Site_List → 200403404
GET
/api/episerver/v3.0/site/{id}
Gets the site with the provided identifier.
Site_Get 1 param → 200403404

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are content (15 properties), contentReference (7 properties), siteDefinition (6 properties), siteDefinitionLanguage (5 properties). Each schema is shown below with its type and property counts.

content
object
15 properties
contentReference
object
7 properties
hostDefinition
object
3 properties
language
object
2 properties
problemDetails
object
5 properties
siteDefinition
object
6 properties
siteDefinitionLanguage
object
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

optimizely-content-management-system-episervercontentapidocs-openapi.json Raw ↑

Other APIs Optimizely publishes across the network.

Optimizely Experimentation REST API v2
Optimizely Feature Experimentation Flags API v1
Optimizely Flags Scheduling API
Optimizely Permission Service API
Optimizely Agent API
Optimizely Event API
Optimizely Edge Decider API
Optimizely Data Platform (ODP) API v3
Optimizely Graph API
Optimizely Content Marketing Platform (CMP) API v3
Optimizely Campaign REST API
Optimizely Configured Commerce API
Where this information came from

This is an independent, third-party profile of Optimizely CMS Content Delivery API v3.0, 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.