Optimizely

Optimizely Sections API

Section management operations

GitHub OpenAPI

Operations 8

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

GET /sections/{id} Get a content section · Fetch section by ID #
Ask an LLM
“Can I fetch the details of a content section by its id?”
“What title, description and query define a given content section?”
Tell an agent
Get content section {id}.
Show the title and query of content section {id}.
PATCH /sections/{id} Update a content section · Update section #
Ask an LLM
“How do I rename a content section or change its description?”
“Can I change the query that decides what content a section shows?”
Tell an agent
Rename content section {id} to {title}.
Set the description of content section {id} to {description} and its query to {query}.
GET /sections/{id}/content List content items in a content section · List section content #
Ask an LLM
“Which content items are assigned to a content section?”
“Can I page through a content section's items and include their topics?”
Tell an agent
List the content in section {id}.
Show page {page} of section {id} content, {rpp} per page, with topics {include_topics}.
GET /experiments/{experiment_id}/sections List sections in a multivariate test · Read all the Sections in a Multivariate Test #
Ask an LLM
“Which sections make up my multivariate test?”
“Can I page through all the sections of a multivariate experiment?”
Tell an agent
List the sections of multivariate test {experiment_id}.
Show page {page} of sections for experiment {experiment_id}, {per_page} per page.
POST /experiments/{experiment_id}/sections Add a section to a multivariate test · Create a new Section in a Multivariate Test #
Ask an LLM
“How do I add a new section with its own variations to a multivariate test?”
“What variations must a new multivariate test section include?”
Tell an agent
Add a section named {name} with variations {variations} to multivariate test {experiment_id}.
Create a new MVT section in experiment {experiment_id} using variations {variations}.
DELETE /experiments/{experiment_id}/sections/{section_id} Archive a multivariate test section · Archive a Section by ID #
Ask an LLM
“How do I archive a section I no longer want in a multivariate test?”
“Does deleting a multivariate test section archive it rather than erase it?”
Tell an agent destructive · confirm first
Archive section {section_id} of multivariate test {experiment_id}.
Remove MVT section {section_id} from experiment {experiment_id}.
GET /experiments/{experiment_id}/sections/{section_id} Get a section of a multivariate test · Read a Section of a Multivariate Test #
Ask an LLM
“Can I read the metadata for one section of a multivariate test?”
“Which variations belong to a particular multivariate test section?”
Tell an agent
Get section {section_id} of multivariate test {experiment_id}.
Show the variations in MVT section {section_id} of experiment {experiment_id}.
PATCH /experiments/{experiment_id}/sections/{section_id} Update a multivariate test section · Update a Section by ID #
Ask an LLM
“Can I rename a multivariate test section or change its variations?”
“Is updating a multivariate section still a beta feature?”
Tell an agent
Rename section {section_id} in multivariate test {experiment_id} to {name}.
Replace the variations of MVT section {section_id} in experiment {experiment_id} with {variations}.

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/optimizely/refs/heads/main/openapi/optimizely-sections-api-openapi.yml

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/optimizely:optimizely-sections-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

optimizely-sections-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: Optimizely Sections API
  version: '1.0'
  description: 'Operations tagged sections across 2 of this provider''s published API definitions: optimizely-recommendations-public-api-spec-openapi.yaml, optimizely-web-experimentation-optimizely-api-openapi.json. Each path carries the servers of the definition it was published in.'
servers:
- url: https://{hostname}/1.0
  description: Primary API server
  variables:
    hostname:
      default: api.usea01.idio.episerver.net
      enum:
      - api.apac01.idio.episerver.net
      - api.caea01.idio.episerver.net
      - api.emea01.idio.episerver.net
      - api.usea01.idio.episerver.net
- url: https://api.optimizely.com/v2
tags:


# --- truncated at 32 KB (33 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/optimizely/refs/heads/main/openapi/optimizely-sections-api-openapi.yml