PlatformConnectAPIs & headless

oneCORE as the engine behind your systems.

The public API gives your developers your products, prices, quotes, orders and customers. Triggers send a webhook the moment something changes, MCP connects your AI tools, and applications on Cloudflare Workers do the work for you. Whatever you build, it works from the same products, rules and prices.

  • Public API in every package
  • Documented in Swagger
  • Webhooks, MCP and Cloudflare Workers for your own logic
oneCORE public API200 OK
GET/api/v2/company/localization
// Example answer: your shop's languages,// currencies and shipping countries{  "languages": ["en", "nl", "de", "fr"],  "currencies": ["EUR", "GBP"],  "shippingCountries": ["NL", "BE", "DE"]}

99.99% platform uptimeLast 90 days, status.colengo.com

What the API covers

Everything you sell, by endpoint.

A selection from oneCORE's changelog. Pick a kind of data to see its endpoints; the full list, with every field, is in the API documentation.

Products & prices

The catalogue, its editions and rules, and the prices of every combination.

  • GETPOST
    /api/v2/productsList products, with their translations, or create a new one.
  • GETPOSTDELETE
    /api/v2/products/{id}/editionsThe editions of a product.
  • GETPOST
    /api/v2/products/{id}/rulesThe rules of a product.
  • GETPOSTPUTPATCHDELETE
    /api/v2/productcombinationpricesCombination prices, filtered by key and value. PUT updates every currency, PATCH one.
  • POST
    /api/v2/render3dQueue 3D renders of a product for a configuration and the angles you choose.
From oneCORE's changelogEvery endpoint and field ↗

Three ways in

Pick the route that fits the job.

Your systems ask oneCORE, oneCORE tells your systems and AI tools, or applications around it do the work. Most setups use more than one.

Public API

Your systems read and write oneCORE's data: products, prices, quotes, orders and customers.

Best for
Keeping your own systems in step with oneCORE
Included
In every package, with API calls under fair use
Docs
colengo.com/api-swagger

Triggers and MCP

oneCORE tells your systems when something changes: a webhook sends the ID of the customer, quote or order. And with MCP, your AI tools connect to oneCORE directly.

Best for
Acting the moment something changes, and connecting your AI tools
Included
Triggers in every package
Example
Order status changed sends the order ID and company URL

Cloudflare Workers

Applications built around oneCORE that do the work for you. They run on Cloudflare Workers and start when something happens.

Best for
Live prices and stock from your ERP, sales orders in your ERP, purchase orders with suppliers
Costs
Scoped in your proposal
Built by
Our team, or your own developers
Status page99.99%platform uptime over the last 90 days
Releases4 daysa week, improvements reach your platform
Colengo15+years building oneCORE, since 2011

For your developers

Build, test, then go live.

Swagger documentation

Every endpoint with its fields. Each shop also shows it at its own /api-swagger.

Sandbox environment

A separate environment to build and test in, as an add-on to your package.

Docker-based testing

One of the cloud features in every package, with 24/7 performance monitoring.

Real-time product feeds

Products and prices for Google Shopping, through feeds and an API connection that passes price changes straight on.

Sign-in with Auth0

Customers and sales users can sign in through Auth0, set up in your API settings.

Protected from abuse

DDoS protection in every package. Scanners and floods of requests can get an HTTP 418 and be blocked.

A Bogard dining table with oak chairs

Customer story · Furniture

An integration built with our AI low-code method.

Bogard's tables are configured on its WooCommerce webshop and on a screen at Loods 5. We built the integration with our AI low-code method, so configurations and orders from both channels sync automatically into Bogard's WooCommerce.

Read the story

Questions

The API and integrations.

Where is the API documentation?

At colengo.com/api-swagger, in Swagger. Each shop also shows it at its own address followed by /api-swagger.

Is the API included in our package?

Yes. The public API is one of the cloud features in every package. API calls fall under a fair use policy.

Can our own developers build on Cloudflare Workers?

Yes. Our project consultant tells you more about how your team can work with it.

What does an integration cost?

What an integration costs to build, and how long it takes, depends on your situation; a project consultant gives you an estimate.

What if we send too many requests?

Requests that look like abuse, such as a vulnerability scanner, far too many requests in a short time or an unusually high number of 404 errors, can get HTTP error 418. In some cases the sender is blocked for a while, or for good.

Can we test without touching the live shop?

Yes, with a sandbox environment, an add-on to your package. See the price list.

What will you connect first?

Book a 30-minute demo with your developer at the table. We'll walk through the API, webhooks, MCP and Cloudflare Workers for your systems.