Optimizely

Optimizely Deliveries API

Delivery management operations

GitHub OpenAPI

Operations 2

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 /deliveries List content recommendation deliveries · List deliveries #
Ask an LLM
“Which widget deliveries are configured for content recommendations?”
“Can I see the API keys for all my deliveries?”
Tell an agent
List all deliveries.
Show every widget delivery with its API key.
GET /deliveries/{key} Get a delivery by its API key · Fetch delivery #
Ask an LLM
“How do I fetch the details of the delivery I'm authenticated as?”
“Can I look up a delivery using its API key?”
Tell an agent
Get delivery {key}.
Show details for the delivery with API key {key}.

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/optimizely/refs/heads/main/openapi/optimizely-deliveries-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-deliveries-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-deliveries-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: Optimizely Content Recommendations Deliveries API
  version: 1.0.0
  contact:
    email: support@optimizely.com
  description: Delivery management operations
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
security:
- key: []
tags:
- name: Deliveries
  description: Delivery management operations
paths:
  /deliveries:
    get:
      operationId: deliveriesList
      summary: List deliveries
      description: Retrieve all widget deliveries, including API keys where applicable.
      tags:
      - Deliveries
      responses:
        '200':
          description: Map of all deliveries
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/DeliveryMap'
        '204':
          description: No active widget deliveries exist
  /deliveries/{key}:
    parameters:
    - $ref: '#/components/parameters/deliveryKey'
    get:
      operationId: deliveryGet
      summary: Fetch delivery
      description: Retrieve detailed information about a delivery using its API key. Use 'me' for the current delivery.
      tags:
      - Deliveries
      responses:
        '200':
          description: Details of a single delivery
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Delivery'
        '404':
          description: Delivery does not exist
components:
  schemas:
    Delivery:
      type: object
      additionalProperties: false
      required:
      - id
      - title
      - active
      - configuration
      - content_selection
      - sections
      description: Represents a content delivery configuration, such as a widget or feed.
      properties:
        id:
          type: integer
          description: Unique identifier of the delivery.
          example: 101
        title:
          type: string
          description: Display title of the delivery.
          example: Homepage Recommendations
        active:
          type: boolean
          description: Indicates whether this delivery is currently active.
          example: true
        configuration:
          $ref: '#/components/schemas/Map'
        content_selection:
          $ref: '#/components/schemas/DeliveryContentSelection'
        sections:
          type: array
          uniqueItems: true
          description: List of sections included in this delivery.
          items:
            $ref: '#/components/schemas/ContentSection'
    DeliveryMap:
      type: object
      description: A map of delivery identifiers to their corresponding API keys.
      properties:
        deliveries:
          type: object
          additionalProperties:
            $ref: '#/components/schemas/Map'
          description: Key-value pairs where key is the delivery ID or name and value is the API key.
    Map:
      type: object
      additionalProperties:
        type: string
    ContentSection:
      type: object
      additionalProperties: false
      required:
      - id
      - title
      - full_details_url
      description: Represents a section that groups related content.
      properties:
        id:
          type: integer
          description: Unique identifier of the section.
          example: 42
        title:
          type: string
          description: The display title of the section.
          example: Technology
        full_details_url:
          type: string
          format: url
          description: API link to fetch full details of this section.
          example: https://api.usea01.idio.episerver.net/1.0/sections/42
    DeliveryContentSelection:
      type: object
      additionalProperties: false
      required:
      - approved
      - featured
      description: Criteria used to select which content is delivered.
      properties:
        approved:
          type: string
          enum:
          - approved
          - unapproved
          - all
          description: Filter content by approval status.
          example: approved
        featured:
          type: string
          enum:
          - featured
          - unfeatured
          - all
          description: Filter content by featured status.
          example: featured
  parameters:
    deliveryKey:
      name: key
      in: path
      required: true
      description: API delivery key. Use `me` to refer to the current delivery.
      schema:
        type: string
      examples:
        me:
          value: me
  securitySchemes:
    key:
      type: apiKey
      in: query
      name: key
      description: API key required for authentication. Must be provided as a query parameter, for example, `?key=YOUR_API_KEY`.