Configurator API reference
The merchant API of the CutOptim Configurator: the calls the embed makes from your shop page, the two checks your server makes before anything reaches a cart, and the signed webhooks your server receives when an order is placed or changes status.
Base URL https://cfg.cutoptim.com · Contract version v1 · OpenAPI 3.1 document
Early access: the merchant API is built and can be tried in a sandbox shop; plug-ins for shop platforms are still in development. CutOptim collects no payment: the cart, the checkout and the payment stay in your shop.
API reference →Full reference for the CutOptim Engine API: endpoints, request and response shapes, every option, error codes, engines, versioning and limits.Three rules behind every integration
The integration is small, but three rules decide whether it is safe. Every page of this reference comes back to them.
- The price comes from the service, never from the browser. The embed shows a price the service computed from your published configuration; a number in a browser event proves nothing.
- Your server verifies before the cart. It sends the quote token to
POST /cfg/v1/quote/verifywith your secret key and looks the order up withGET /cfg/v1/orders/{id}. - A webhook is trusted only after its signature checks out over the raw bytes you received, and it is processed once per event id.
Where to start
New to the Configurator? Read the Quickstart first, then Keys and authentication. The Endpoints page lists every route; the OpenAPI document behind it is the machine-readable contract your code generator can read.
There is no "try it" button here on purpose: the secret key belongs on your server, never in a browser. The demo shop shows the embed and the order hand-off working end to end.
LegalConfigurator terms ·Data processing agreement ·Shopper privacy notice ·Third-party licences