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 Customer Orders API

The Customer Orders API from Optimizely — 14 operation(s) for customer orders.

Optimizely Customer Orders API is one of 420 APIs that Optimizely publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Customer Orders. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 18 operations across 14 paths, and defines 2 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.

18 operations 14 paths 2 schemas 2 DELETE13 GET1 PATCH1 POST1 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 Customer Orders 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 18

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

Customer Orders 18
GET
/api/v1/admin/CustomerOrders
Returns the EntitySet CustomerOrders
CustomerOrders_Get 8 params → 200
POST
/api/v1/admin/CustomerOrders
Post a new entity to EntitySet CustomerOrders
CustomerOrders_Post body → 200
GET
/api/v1/admin/CustomerOrders({id})
Returns the entity with the key from CustomerOrders
CustomerOrders_GetById 3 params → 200
PUT
/api/v1/admin/CustomerOrders({id})
Replace entity in EntitySet CustomerOrders
CustomerOrders_PutById 1 param body → 200
DELETE
/api/v1/admin/CustomerOrders({id})
Delete entity in EntitySet CustomerOrders
CustomerOrders_DeleteById 2 params → 200
PATCH
/api/v1/admin/CustomerOrders({id})
Update entity in EntitySet CustomerOrders
CustomerOrders_PatchById 1 param body → 200
GET
/api/v1/admin/CustomerOrders/Default.Default()
Call operation Default
CustomerOrders_Default → 200
GET
/api/v1/admin/CustomerOrders({id})/Default.Totals()
Call operation Totals
CustomerOrders_TotalsById 1 param → 200
GET
/api/v1/admin/customerorders({key})/totals
CustomerOrders_TotalsByKey 1 param → 200
DELETE
/api/v1/admin/customerorders/delete
CustomerOrders_DeleteRoute 1 param → 200
GET
/api/v1/admin/customerorders({key})/creditcardtransactions({creditcardtransactionKey})
CustomerOrders_GetCreditCardTransactionByKeyAndCreditcardtransactionkey 4 params → 200
GET
/api/v1/admin/customerorders({key})/customerorderpromotions({customerorderpromotionKey})
CustomerOrders_GetCustomerOrderPromotionByKeyAndCustomerorderpromotionkey 4 params → 200
GET
/api/v1/admin/customerorders({key})/customerordertaxes({customerordertaxKey})
CustomerOrders_GetCustomerOrderTaxByKeyAndCustomerordertaxkey 4 params → 200
GET
/api/v1/admin/customerorders({key})/customproperties({custompropertyKey})
CustomerOrders_GetCustomPropertyByKeyAndCustompropertykey 4 params → 200
GET
/api/v1/admin/customerorders({key})/giftcards({giftcardKey})
CustomerOrders_GetGiftCardByKeyAndGiftcardkey 4 params → 200
GET
/api/v1/admin/customerorders({key})/orderlines({orderlineKey})
CustomerOrders_GetOrderLineByKeyAndOrderlinekey 4 params → 200
GET
/api/v1/admin/customerorders({key})/orderpromotioncodes({orderpromotioncodeKey})
CustomerOrders_GetOrderPromotionCodeByKeyAndOrderpromotioncodekey 4 params → 200
GET
/api/v1/admin/customerorders({key})/subscriptions({subscriptionKey})
CustomerOrders_GetSubscriptionByKeyAndSubscriptionkey 4 params → 200

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are Insite.Data.Entities.CustomerOrder (104 properties), Insite.Admin.Controllers.OData.OrderTotal (7 properties). Each schema is shown below with its type and property counts.

Insite.Admin.Controllers.OData.OrderTotal
object
7 properties
Insite.Data.Entities.CustomerOrder
object
104 properties 53 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

optimizely-customer-orders-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 Customer Orders 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.