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 User Profiles API

The User Profiles API from Optimizely — 26 operation(s) for user profiles.

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

This API exposes 33 operations across 26 paths, and defines 5 schemas. It is described by OpenAPI 3.2.0, at version admin-v1.

Requests are made against a single base URL, https://dogfood.commerce.insitesandbox.com.

33 operations 26 paths 5 schemas 3 DELETE25 GET1 PATCH2 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
admin-v1
Base URL
https://exp.mcp.opal.optimizely.com/mcp
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Optimizely User Profiles API declares 1 security scheme for authenticating requests. An API key is passed in the query as access_token (access_token).

  • access_token — Token used to access storefront API.

Paths & Operations 33

Across 26 paths, the API surfaces 33 operations — 3 DELETE, 25 GET, 1 PATCH, 2 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

User Profiles 33
GET
/api/v1/admin/UserProfiles
Returns the EntitySet UserProfiles
UserProfiles_Get 8 params → 200
POST
/api/v1/admin/UserProfiles
Post a new entity to EntitySet UserProfiles
UserProfiles_Post body → 200
GET
/api/v1/admin/UserProfiles({id})
Returns the entity with the key from UserProfiles
UserProfiles_GetById 3 params → 200
PUT
/api/v1/admin/UserProfiles({id})
Replace entity in EntitySet UserProfiles
UserProfiles_PutById 1 param body → 200
DELETE
/api/v1/admin/UserProfiles({id})
Delete entity in EntitySet UserProfiles
UserProfiles_DeleteById 2 params → 200
PATCH
/api/v1/admin/UserProfiles({id})
Update entity in EntitySet UserProfiles
UserProfiles_PatchById 1 param body → 200
GET
/api/v1/admin/UserProfiles/Default.Default()
Call operation Default
UserProfiles_Default → 200
GET
/api/v1/admin/UserProfiles({id})/Default.Roles()
Call operation Roles
UserProfiles_GetRolesById 9 params → 200
GET
/api/v1/admin/UserProfiles/Default.Current()
Call operation Current
UserProfiles_Current_1 2 params → 200
GET
/api/v1/admin/userprofiles/current
UserProfiles_Current_2 2 params → 200
GET
/api/v1/admin/userprofiles({key})/roles
UserProfiles_GetRolesByKey 9 params → 200
PUT
/api/v1/admin/userprofiles({key})/roles
UserProfiles_SetRolesByKey_1 1 param body → 200
POST
/api/v1/admin/userprofiles({key})/roles
UserProfiles_SetRolesByKey_2 1 param body → 200
DELETE
/api/v1/admin/userprofiles({key})/roles
UserProfiles_DeleteRolesByKey 1 param body → 200
GET
/api/v1/admin/userprofiles({key})/allowedwebsites
UserProfiles_AllowedWebsitesByKey 9 params → 200
GET
/api/v1/admin/userprofiles({key})/approvers
UserProfiles_ApproversByKey 9 params → 200
GET
/api/v1/admin/userprofiles({key})/availablecustomers
UserProfiles_AvailableCustomersByKey 9 params → 200
DELETE
/api/v1/admin/userprofiles/delete
UserProfiles_DeleteRoute 1 param → 200
GET
/api/v1/admin/userprofiles({key})/customers({customerKey})
UserProfiles_GetCustomerByKeyAndCustomerkey 4 params → 200
GET
/api/v1/admin/userprofiles({key})/customproperties({custompropertyKey})
UserProfiles_GetCustomPropertyByKeyAndCustompropertykey 4 params → 200
GET
/api/v1/admin/userprofiles({key})/dashboardpanelpositions({dashboardpanelpositionKey})
UserProfiles_GetDashboardPanelPositionByKeyAndDashboardpanelpositionkey 4 params → 200
GET
/api/v1/admin/userprofiles({key})/emaillists({emaillistKey})
UserProfiles_GetEmailListByKeyAndEmaillistkey 4 params → 200
GET
/api/v1/admin/userprofiles({key})/messagestatuses({messagestatusKey})
UserProfiles_GetMessageStatusByKeyAndMessagestatuskey 4 params → 200
GET
/api/v1/admin/userprofiles({key})/odppersonas({personaKey})
UserProfiles_GetOdpPersonaByKeyAndPersonakey 4 params → 200
GET
/api/v1/admin/userprofiles({key})/salespersons({salespersonKey})
UserProfiles_GetSalespersonByKeyAndSalespersonkey 4 params → 200
GET
/api/v1/admin/userprofiles({key})/userpaymentprofiles({userpaymentprofileKey})
UserProfiles_GetUserPaymentProfileByKeyAndUserpaymentprofilekey 4 params → 200
GET
/api/v1/admin/userprofiles({key})/userprofilepasswords({userprofilepasswordKey})
UserProfiles_GetUserProfilePasswordByKeyAndUserprofilepasswordkey 4 params → 200
GET
/api/v1/admin/userprofiles({key})/userprofilewishlistfavorites({userprofilewishlistfavoriteKey})
UserProfiles_GetUserProfileWishListFavoriteByKeyAndUserprofilewishlistfavoritekey 4 params → 200
GET
/api/v1/admin/userprofiles({key})/userprofilewishlisthides({userprofilewishlisthideKey})
UserProfiles_GetUserProfileWishListHideByKeyAndUserprofilewishlisthidekey 4 params → 200
GET
/api/v1/admin/userprofiles({key})/userprofilewishlisttags({userprofilewishlisttagKey})
UserProfiles_GetUserProfileWishListTagByKeyAndUserprofilewishlisttagkey 4 params → 200
GET
/api/v1/admin/userprofiles({key})/websites({websiteKey})
UserProfiles_GetWebsiteByKeyAndWebsitekey 4 params → 200
GET
/api/v1/admin/userprofiles({key})/wishlistproducts({wishlistproductKey})
UserProfiles_GetWishListProductByKeyAndWishlistproductkey 4 params → 200
GET
/api/v1/admin/userprofiles({key})/wishlists({wishlistKey})
UserProfiles_GetWishListByKeyAndWishlistkey 4 params → 200

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are Insite.Data.Entities.UserProfile (40 properties), ODataResponseStringList (2 properties), ODataResponseWebsiteList (1 property), ODataResponseCustomerList (1 property). Each schema is shown below with its type and property counts.

Insite.Data.Entities.UserProfile
object
40 properties 11 required
ODataResponseUserProfileList
object
1 property
ODataResponseCustomerList
object
1 property
ODataResponseStringList
object
2 properties
ODataResponseWebsiteList
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

optimizely-user-profiles-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 User Profiles 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.