Changelog

Dated newest first. Every entry names what an integration has to do, if anything.

2026-11-08: the Channel API reference

This reference is published: 89 endpoints over customers, channels, products, catalog, inventory, orders, fulfillment orders, the fulfillment queue, shipments, invoices, payments, purchase orders, vendors, operations and batch, with the scope, idempotency and rate-limit notes on each one and request examples on the main writes.
The Channel API scopes (channel:read, channel:write and the per-resource write scopes) appear in the OS portal under Users > Permission groups > Channel API, so an API key can be limited to exactly what an integration does. Keys that hold admin or the older *:manage scopes keep working unchanged.
The legacy Channel API (api.kentro.live/v1/channel/*) is deprecated. It keeps answering for existing integrations, its reference is withdrawn from this site, and Migrating from the legacy Channel API maps each call to its replacement. No action is required to keep an existing integration running.

Every api.kentro.live/v1/channel/* call is answered by the new platform through a compatibility layer that translates the legacy request and answer shapes. Behavior differences that reached integrations: a line that names a product group instead of a variant is refused (INVENTORY_ITEM_NOT_FOUND in the legacy shape), and a cancel of an order with shipped units is refused. Both were silent data problems before.

Orders, invoices and payments created by Kentro's own integrations (Shopify, WooCommerce, Amazon, EDI retailers, 3PLs) moved to the new API. Documents keep their ids; a record created before the move is read and written by both APIs.