The two Kentro APIs, which one a project needs, how authentication works and where to get help.
Kentro is the operating system for B2B commerce: one system of record for orders, customers, products, inventory, fulfillment, shipping, invoices and payments across every sales channel a tenant runs, with storefronts, a 3PL network and EDI on top. Everything the Kentro OS portal does, these two APIs do for a system or a storefront the tenant builds.
Channel API
The Channel API moves a sales channel's data into and out of Kentro: orders, customers, products and listings, inventory, fulfillment orders, shipments, invoices, payments and purchase orders. It is for integrations: marketplaces, carts, EDI, 3PLs, ERPs and WMSs. Kentro is the system of record; the caller is a system.
- Base URL:
https://apis.kentro.live/channel/v1(sandboxhttps://apis.kentro.dev/channel/v1) - Start here: Channel API: Getting started
Store API
The Store API is Kentro's storefront infrastructure (buyer sign-in, the catalog with the buyer's prices, cart, quotes, checkout, orders, invoices, account, subscriptions) for a tenant who builds their own storefront UI instead of using the templates in Kentro OS > Storefront. The caller is the tenant's storefront server, acting for one buyer at a time.
- Base URL:
https://apis.kentro.live/store/v1(sandboxhttps://apis.kentro.dev/store/v1) - Start here: Store API: Getting started
Authentication at a glance
Both APIs are opened by an API key created in Kentro OS under Users > API keys. A key belongs to one tenant and carries the scopes of its permission groups: channel:read and channel:write for the Channel API, storefront:serve for the Store API, admin for both.
- Channel API: send the key pair as
kentro-keyandkentro-secret, or exchange it for a 15-minute bearer token atPOST https://apis.kentro.live/auth/login/api-key. - Store API: send
X-API-KeyandX-Storefront-Hoston every call; the buyer's token fromPOST https://apis.kentro.live/auth/login/customertravels asX-Storefront-Buyer.
Nothing in a request selects a tenant; the key's tenant is the tenant of every call.
Support
Questions and refusals go to [email protected] with the request id from the response (X-Request-Id or requestId) and the message returned. Incident and maintenance notices come from the same address.
Legacy APIs
The legacy Channel API (api.kentro.live/v1/channel/*) and the legacy Store API (api.kentro.live/v1/store/*) keep answering for the callers that use them, receive no changes, and are retired once every caller has moved. Their references were withdrawn from this site. Each call is mapped to its replacement in Migrating from the legacy Channel API and Migrating from the legacy Store API.