Episerver website screenshot

Episerver

Episerver is a digital experience platform (DXP) vendor that rebranded to Optimizely in 2021 after Episerver acquired Optimizely; the developer surface now ships under the Optimizely brand. The platform combines content management (CMS / Content Cloud), a headless Content Delivery and Content Management REST API, the Optimizely Graph (Content Graph) GraphQL API, Commerce (Configured Commerce and Commerce Connect), Feature Experimentation and Web Experimentation, the Optimizely Data Platform (ODP), the Content Marketing Platform (CMP), and Opti ID for unified OIDC identity. Developers integrate via first-party SDKs for JavaScript, React, Python, Java, C#/.NET, Ruby, PHP, Go and Swift, the EPiServer.CMS .NET libraries on NuGet, REST and GraphQL APIs, and webhooks. This profile was seeded as a portfolio lead and enriched by the API Evangelist pipeline from Optimizely's public developer documentation.

Episerver publishes 3 APIs on the APIs.io network. Tagged areas include Company, Enterprise, Content Management, Digital Experience Platform, and CMS.

The Episerver catalog on APIs.io includes 1 event-driven AsyncAPI specification.

Episerver’s developer surface includes documentation, API reference, getting-started guide, support, engineering blog, pricing, authentication, and 21 more developer resources.

45.1/100 developing ▬ flat Agent 19/100 agent aware Full breakdown ↓
scored 2026-07-27 · rubric v0.5
AccessSelf serve
3 APIs
CompanyEnterpriseContent ManagementDigital Experience PlatformCMSCommerceExperimentationPersonalizationGraphQLSDKs

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 45.1/100 · developing
Contract Quality 5.7 / 25
Developer Ergonomics 11.7 / 20
Commercial Clarity 9.5 / 20
Operational Transparency 8.2 / 13
Governance 0.0 / 12
Discoverability 10.0 / 10
Agent readiness — 19/100 · agent aware
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 0 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 6 / 6
Agent Skills 0 / 5
Well-Known Catalog 4 / 4
Consent & Bot Identity 0 / 3
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/episerver: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 3

Individual APIs this provider publishes, each with its own machine-readable definition.

Optimizely Graph (Content Graph)

GraphQL Content Graph API that indexes CMS/Commerce content for fast, federated querying across the Optimizely platform.

Optimizely Feature Experimentation REST API

REST API and multi-language SDKs for feature flags, experimentation and rollouts, with the self-hosted Optimizely Agent as a microservice front end.

Content Management REST API (CMS 12)

Headless Content Delivery, Content Management and Content Definitions REST APIs for the Optimizely (Episerver) CMS.

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Security Posture 4

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Episerver Authentication

oauth2/openIdConnect/apiKey/http · 6 schemes

SECURITY

Episerver Domain Security

TLSv1.2 · HSTS · DMARC

SECURITY

Episerver Vulnerability Disclosure

disclosure policy published

SECURITY

Episerver Trust Center

SOC 2, ISO 27001, ISO 27017, ISO 27018, PCI DSS, HIPAA

SECURITY

Resources

Get Started 2

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 4

Pagination, idempotency, versioning, errors, and events

Build 3

SDKs, sample code, and the tooling you integrate with

Access & Security 6

Authentication, authorization, and security posture

Operate 4

Status, limits, changes, and where to get help

Commercial 3

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: episerver
name: Episerver
description: Episerver is a digital experience platform (DXP) vendor that rebranded to Optimizely in 2021 after Episerver
  acquired Optimizely; the developer surface now ships under the Optimizely brand. The platform combines content management
  (CMS / Content Cloud), a headless Content Delivery and Content Management REST API, the Optimizely Graph (Content Graph)
  GraphQL API, Commerce (Configured Commerce and Commerce Connect), Feature Experimentation and Web Experimentation, the Optimizely
  Data Platform (ODP), the Content Marketing Platform (CMP), and Opti ID for unified OIDC identity. Developers integrate via
  first-party SDKs for JavaScript, React, Python, Java, C#/.NET, Ruby, PHP, Go and Swift, the EPiServer.CMS .NET libraries
  on NuGet, REST and GraphQL APIs, and webhooks. This profile was seeded as a portfolio lead and enriched by the API Evangelist
  pipeline from Optimizely's public developer documentation.
url: https://raw.githubusercontent.com/api-evangelist/episerver/refs/heads/main/apis.yml
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  generated: '2026-07-22'
  method: derived
image: https://logo.clearbit.com/optimizely.com
x-type: company
x-source: vc-portfolio
x-backed-by:
- northzone
x-tier: stub
x-tier-reason: portfolio-lead
x-rebranded-to: Optimizely
specificationVersion: '0.20'
created: '2026-07-17'
modified: '2026-07-19'
tags:
- Company
- Enterprise
- Content Management
- Digital Experience Platform
- CMS
- Commerce
- Experimentation
- Personalization
- GraphQL
- SDKs
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
apis:
- name: Optimizely Graph (Content Graph)
  description: GraphQL Content Graph API that indexes CMS/Commerce content for fast, federated querying across the Optimizely
    platform.
  humanURL: https://docs.developers.optimizely.com/platform-optimizely/docs/optimizely-graph
  baseURL: https://cg.optimizely.com
  properties:
  - type: GraphQL
    url: https://docs.developers.optimizely.com/platform-optimizely/docs/optimizely-graph
  - type: Authentication
    url: authentication/episerver-authentication.yml
- name: Optimizely Feature Experimentation REST API
  description: REST API and multi-language SDKs for feature flags, experimentation and rollouts, with the self-hosted Optimizely
    Agent as a microservice front end.
  humanURL: https://docs.developers.optimizely.com/feature-experimentation
  baseURL: https://api.optimizely.com
  properties:
  - type: SDKs
    url: packages/episerver-packages.yml
- name: Content Management REST API (CMS 12)
  description: Headless Content Delivery, Content Management and Content Definitions REST APIs for the Optimizely (Episerver)
    CMS.
  humanURL: https://docs.developers.optimizely.com/content-management-system/reference
  baseURL: https://cg.optimizely.com
  properties:
  - type: Documentation
    url: https://docs.developers.optimizely.com/content-management-system/reference
common:
- type: Website
  url: https://www.optimizely.com
- type: DeveloperPortal
  url: https://docs.developers.optimizely.com
- type: Documentation
  url: https://docs.developers.optimizely.com
- type: APIReference
  url: https://docs.developers.optimizely.com/content-management-system/reference
- type: GettingStarted
  url: https://docs.developers.optimizely.com/getting-started
- type: Support
  url: https://support.optimizely.com
- type: Blog
  url: https://www.optimizely.com/insights/blog/
- type: GitHubOrganization
  url: https://github.com/optimizely
- type: StatusPage
  url: https://status.optimizely.com
- type: Deprecation
  url: https://docs.developers.optimizely.com/deprecated-products/docs/deprecated-products
- type: Pricing
  url: https://www.optimizely.com/pricing/
- type: TermsOfService
  url: https://www.optimizely.com/legal/website-terms-of-use/
- type: PrivacyPolicy
  url: https://www.optimizely.com/privacy-policy/
- type: Compliance
  url: https://www.optimizely.com/trust-center/compliance
- type: TrustCenter
  url: security/episerver-trust-center.yml
- type: Security
  url: https://www.optimizely.com/trust-center/security
- type: Packages
  url: packages/episerver-packages.yml
- type: SDKs
  url: packages/episerver-packages.yml
- type: LLMsTxt
  url: llms/episerver-llms.txt
- type: WellKnown
  url: well-known/episerver-well-known.yml
- type: Authentication
  url: authentication/episerver-authentication.yml
- type: Lifecycle
  url: lifecycle/episerver-lifecycle.yml
- type: ChangeLog
  url: changelog/episerver-changelog.yml
- type: Conventions
  url: conventions/episerver-conventions.yml
- type: Conformance
  url: conformance/episerver-conformance.yml
- type: Webhooks
  url: asyncapi/episerver-webhooks.yml
- type: DomainSecurity
  url: security/episerver-domain-security.yml
- type: VulnerabilityDisclosure
  url: security/episerver-vulnerability-disclosure.yml
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence