Optimizely API
Browse all Optimizely APIs★ Only Publicly Available OpenAPI DocumentAnalyticsProduct AnalyticsapiKey3 EndpointsREST
For Agents
Authenticate to the Optimizely developers platform and list resource endpoints, providing a discovery starting point for agents calling Optimizely product APIs.
Use for: Get an Optimizely access token from my client credentials, List the resources available to my Optimizely application, Retrieve a specific Optimizely resource by ID, Check whether my Optimizely API key is valid
Not supported: Does not handle running experiments, managing audiences, or content delivery — use for Optimizely developer auth and resource discovery only.
Jentic publishes the only available OpenAPI specification for this Optimizely Developers API surface, keeping it validated and agent-ready. Optimizely is a digital experience optimisation platform covering experimentation, content management, and personalisation. This minimal slice exposes the OAuth-style token endpoint and a generic resources directory, intended as a starting point for agents authenticating to the Optimizely platform and discovering available resources before calling product-specific APIs. Authentication uses an API key sent in the Authorization header.
Install Jentic One Beta
Connect the Optimizely API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Optimizely API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Optimizely API.
Exchange platform credentials for an Optimizely access token via the auth endpoint
List available resource entries the calling credential can reach on the Optimizely developers surface
Look up a single resource entry by ID to inspect its metadata before deeper integration
Verify an API key is valid before driving downstream calls into other Optimizely APIs
Use Cases
Patterns agents use Optimizely API for, with concrete tasks.
★ Bootstrap auth for Optimizely integrations
Engineering teams beginning a new Optimizely integration use POST /auth/token as the first call to exchange their application credentials for an access token. The token is then reused across the rest of the Optimizely product APIs (Web Experimentation, Feature Experimentation, Optimizely Data Platform). This minimal spec is well suited to scripted onboarding and credential sanity-checks.
POST /auth/token with the application client_id and client_secret and store the returned access_token for downstream calls.
Resource discovery before deeper calls
Agents that wrap multiple Optimizely surfaces can use GET /resources to discover which resource entries the calling credential can reach before deciding which product-specific endpoints to call. GET /resources/{id} retrieves a single entry's metadata, which is useful when the agent only has an ID and needs to confirm what it points to.
GET /resources to enumerate accessible entries, then GET /resources/{id} for the specific resource the user asked about.
Credential sanity checks in CI
CI pipelines deploying Optimizely-aware applications can run POST /auth/token as a pre-deploy sanity check so that a misconfigured key fails the build rather than failing in production. The check requires no test data and produces a quick yes/no on credential validity.
POST /auth/token in the pre-deploy job and fail the build if a 401 response is returned.
AI agent bootstrap for Optimizely
Through Jentic, an agent that needs to integrate with multiple Optimizely surfaces can load this minimal API first to verify credentials and resource visibility before the user wires it into the larger Optimizely Web Experimentation API. The vaulted API key is supplied at execution, so the agent never handles the secret itself.
Search Jentic for 'get an optimizely access token', execute POST /auth/token, and pass the returned token to subsequent Optimizely calls.
Key Endpoints
3 endpoints — jentic publishes the only available openapi specification for this optimizely developers api surface, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/auth/token
Get an access token
GET
/resources
List available resources
GET
/resources/{id}
Get a single resource by ID
POST
/auth/token
Get an access token
GET
/resources
List available resources
GET
/resources/{id}
Get a single resource by ID
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Optimizely API keys are stored encrypted in the Jentic vault. Agents receive a scoped execution context — the key is added as the Authorization header at request time and never appears in agent prompts or logs.
Intent-based discovery
Agents search Jentic with intents like 'get an optimizely access token' and Jentic returns POST /auth/token with its input schema, ready to execute against the vaulted credential.
Time to first call
Direct integration: a couple of hours to read the developers docs and wire token handling. Through Jentic: under 15 minutes — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Optimizely API through Jentic.
Why is there no official OpenAPI spec for Optimizely API?
Optimizely does not publish a single canonical OpenAPI specification covering this developers surface. Jentic generates and maintains this spec so that AI agents and developers can call Optimizely API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does this Optimizely API use?
It uses an API key passed in the Authorization header. Through Jentic the key is stored encrypted in the vault and added to the header at request time, so the agent never sees the credential itself.
Can I run experiments through this API?
No. This three-endpoint slice handles auth and resource discovery only. Running experiments uses Optimizely's separate Web Experimentation API, which is published as the Optimizely v2 spec under optimizely.com/optimizely-api in this catalogue.
What are the rate limits for the Optimizely developers API?
Optimizely applies rate limits at the platform level rather than per endpoint in this slice. Treat 429 responses as a signal to back off and consult the Optimizely developer documentation for the limits attached to your subscription tier.
How do I get an access token through Jentic?
Search Jentic for 'get an optimizely access token', load POST /auth/token, and execute it. The vaulted credential is supplied automatically and the response includes the access_token to pass to other Optimizely APIs.
What does the resources endpoint return?
GET /resources returns a list of accessible resource entries on the developers surface, with metadata an agent can use to decide which downstream Optimizely product API to call. GET /resources/{id} returns the same metadata for a single entry.
GET STARTED