Developer changelog

Each entry names what changed and what an integration has to do, if anything. The per-API changelogs, Channel API, Store API and the Pixel changelog, keep the full detail.

2026-11-09: the developer center

• The documentation moves from a single API Reference section to this developer center: Get started, Integration guides, Build with AI, Kentro MCP and Resources in the Guides section, and the Channel API, Store API and Kentro Pixel references in the API Reference section. Reference pages keep their addresses.
• The Kentro Pixel reference is split into topic pages: overview, quickstart, domains, browser SDK, events, server API, identity, consent and privacy, destinations, limits and errors, and a changelog. /reference/kentro-pixel stays the overview.

2026-11-08: Channel API reference and scopes

• The Channel API 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.
• The Channel API scopes (channel:read, channel:write and one write scope per resource) appear in Kentro OS under Users > Permission groups. Keys holding admin or the older *:manage scopes keep working unchanged.

2026-11-08: Store API reference and public access

• The Store API reference is published, with the storefront operations over store, session, catalog, cart, checkout, orders, invoices, account, addresses, payments, carriers, applications, subscriptions and fulfillment.
• The Store API is reachable at https://apis.kentro.live/store/v1 with a tenant API key whose permission group holds the new storefront:serve scope (or admin). Buyer sign-in, refresh, sign-out and password reset use https://apis.kentro.live/auth.

2026-11-07: Store API sign-up records marketing consent

• session.signup accepts marketingOptIn. When it is true and the sign-up has an email address, Kentro records the buyer's opt-in to marketing email; a phone-only sign-up has nothing to opt in. Action: send the value of the sign-up form's marketing checkbox.

2026-11-05: order-less payments apply to their invoice's order

• POST /v1/payments/:id/apply with invoices but no order answered 409 payment_without_order. A payment is now applied when every invoice it names belongs to one order in the payment's sales channel. Invoices of several orders still need the order named. No action is required.