Optimizely 📝 Resources API
The 📝 Resources API from Optimizely — 2 operation(s) for 📝 resources.
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.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/optimizely-resources-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.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
title: Optimizely Graph 📝 Resources API
version: 3.24.0
description: Optimizely Graph API definition
license:
name: ' '
contact:
name: Documentation
url: https://cg.optimizely.com/
servers:
- url: https://prod.cg.optimizely.com
tags:
- name: Resources
paths:
/resources/stopwords:
put:
operationId: upsert-StopwordHandler
responses:
'204':
description: No content
description: Stop words are the words in a stop list (or stop list or negative dictionary) which are filtered out (stopped) before or after processing of natural language data (text) because they are insignificant
summary: Store stop words
tags:
- Resources
security:
- epi-hmac: []
- Basic: []
- Bearer: []
parameters:
- in: query
name: language_routing
required: false
schema:
type: string
- in: query
name: source_routing
required: false
schema:
type: string
requestBody:
required: true
content:
text/plain:
schema:
$ref: '#/components/schemas/StopwordsBody'
delete:
operationId: delete-StopwordHandler
responses:
'204':
description: No content
summary: Delete stop words
tags:
- Resources
security:
- epi-hmac: []
- Basic: []
- Bearer: []
parameters:
- in: query
name: language_routing
required: false
schema:
type: string
- in: query
name: source_routing
required: false
schema:
type: string
/resources/synonyms:
get:
operationId: list-SynonymHandler
responses:
'200':
description: Ok
content:
application/json:
schema:
$ref: '#/components/schemas/Response'
description: Get synonyms for a given slot
summary: List synonyms
tags:
- Resources
security:
- epi-hmac: []
- Basic: []
- Bearer: []
parameters:
- in: query
name: language_routing
required: false
schema:
type: string
- in: query
name: source_routing
required: false
schema:
type: string
- in: query
name: synonym_slot
required: false
schema:
default: one
type: string
enum:
- one
- two
put:
operationId: upsert-SynonymHandler
responses:
'204':
description: No content
description: 'When you write a query, you can use synonyms to expand the keywords to get results that users otherwise may not have found.
This reduces the problem of getting too few or no results, leading to fewer chances of conversions or even search abandonment.
For example, if you search for "H2O", you mat want to find results that contain "water".
This happens when you store synonyms in Optimizely Graph and enable them per field in your query. Otherwise, many relevant results may not be retrieved.'
summary: Store synonyms
tags:
- Resources
security:
- epi-hmac: []
- Basic: []
- Bearer: []
parameters:
- in: query
name: language_routing
required: false
schema:
type: string
- in: query
name: source_routing
required: false
schema:
type: string
- in: query
name: synonym_slot
required: false
schema:
default: one
type: string
enum:
- one
- two
requestBody:
required: true
content:
text/plain:
schema:
$ref: '#/components/schemas/SynonymsBody'
delete:
operationId: delete-SynonymHandler
responses:
'204':
description: No content
summary: Delete synonyms
tags:
- Resources
security:
- epi-hmac: []
- Basic: []
- Bearer: []
parameters:
- in: query
name: language_routing
required: false
schema:
type: string
- in: query
name: source_routing
required: false
schema:
type: string
components:
schemas:
Response:
description: 'This Fetch API interface represents the response to a request.
[MDN Reference](https://developer.mozilla.org/docs/Web/API/Response)'
properties: {}
type: object
additionalProperties: false
SynonymsBody:
type: string
example: 'H20 => water
Siteseeker, Welcome, Episerver => Optimizely
William Henry Gates III => Bill Gates'
StopwordsBody:
type: string
example: 'the
Schwarzenegger
amy
Bob'
securitySchemes:
epi-single:
type: apiKey
name: auth
in: query
description: Single key authentication
epi-hmac:
type: apiKey
name: Authorization
in: header
description: HMAC authentication (`epi-hmac xxx`)
Basic:
type: http
scheme: basic
description: HMAC credentials
Bearer:
type: http
scheme: bearer
bearerFormat: JWT
description: JWT token