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 Users API

User Management

Optimizely Users API is one of 420 APIs that Optimizely publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include User. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 10 operations across 7 paths, and defines 27 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 3 base URLs: https://api.campaign.episerver.net/rest, https://api.cmp.optimizely.com/v3, https://{hostname}/1.0.

10 operations 7 paths 27 schemas 1 DELETE5 GET3 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, OAuth 2.0, API Key
Resource Areas
1

Authentication & Security 3

Optimizely Users API declares 3 security schemes for authenticating requests. An API key is passed in the header as Authorization (Authorization). It supports OAuth 2.0 (OAuth2) using the authorizationCode and clientCredentials flows, exposing 3 scopes. An API key is passed in the query as key (key).

  • key — API key required for authentication. Must be provided as a query parameter, for example, ?key=YOURAPIKEY.

Paths & Operations 10

Across 7 paths, the API surfaces 10 operations — 1 DELETE, 5 GET, 3 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Users 10

User Management

GET
/{clientId}/users/authenticated
Get basic information of an authenticated user.
getAuthenticatedUser 1 param → 200
POST
/{clientId}/users/rotatepassword
Rotate a password. Please be aware that after rotation it can take some minutes until the new password can be used.
rotatePassword 1 param body → 202400
GET
/userlist
GET /userlist
listUsers 2 params → 200400401403404
GET
/users
GET /users
findUserByEmail 1 param → 302400401403404
POST
/users
Create a new user
userCreate body → 201
GET
/users/{id}
GET /users/{id}
getUser 2 params → 200400401403404
PUT
/users/{id}
Update user
userUpdate 1 param body → 200404
DELETE
/users/{id}
Delete user
userDelete 1 param → 200404
GET
/users/{id}/content
Fetch personalised content
userContentList 6 params → 200204404
POST
/users/{id}/content/_filter
Search user content
userContentSearch 4 params body → 200204404

Schemas 27

The contract defines 27 schemas that model the data the API accepts and returns. The most detailed are ContentItemMinimal (7 properties), UserResponse (7 properties), UserListResponseItem (7 properties), UserCore (6 properties). Each schema is shown below with its type and property counts.

UserRequestData
object
2 properties 2 required
AuthenticatedUser
object
3 properties
RestUser
object
2 properties
UserListResponseItem
object
7 properties 7 required
Error
object
Error payload
2 properties 1 required
UserResponse
object
7 properties 6 required
UserListResponse
object
2 properties 2 required
Pagination
object
Pagination related information
2 properties 2 required
UserContentList
UserCore
object
6 properties 1 required
ContentTopic
object
3 properties 3 required
ContentItem
UserPartial
UserStub
object
2 properties 2 required
ContentItemMinimal
object
7 properties
List
object
Base pagination metadata object.
3 properties 1 required
ServiceCredential
object
1 property 1 required
ContentMainImage
object
2 properties 2 required
Map
object
Message
object
Generic message response object returned by the API.
1 property 1 required
ContentAuthor
object
3 properties 3 required
ContentSource
object
The source (origin) of the content.
4 properties 4 required
ContentList
A paginated list of content items with navigation metadata.
User
ContentQuery
object
Object containing a Lucene query string used to search or filter content.
1 property 1 required
ContentMetadata
object
Metadata for a content item, such as language and tags.
2 properties
ServiceCredentials
array

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

optimizely-users-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 Users 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.