Glossary
The terms used across Kentro's developer center and API references, each defined in a sentence, with where to read more.
The terms below appear across the developer center and the API references. Each entry gives the meaning on Kentro and where to read more.
| Term | Meaning |
|---|---|
admin | The scope that grants everything in a tenant, both APIs included. |
| API key | A tenant's credential for a system, created in Kentro OS under Users > API keys: a public key and a secret shown once. See API keys and scopes. |
| Application (payment) | The part of a payment applied to one invoice; one payment can have several. |
| Application (storefront) | A prospective buyer's request for an account, submitted through application.* and decided by staff in Kentro OS. |
| Batch | POST /v1/batch: up to 100 Channel API operations in one request, each run on its own, not atomic. |
| Bearer token | A 15-minute access token minted from an API key pair at POST /auth/login/api-key, sent as Authorization: Bearer. |
| Buyer | A signed-in customer on a storefront, identified by a buyer token in X-Storefront-Buyer. |
| Cart revision | revision on every Store API cart answer; mutations send it back as expectedRevision, and a stale one answers 409 CONFLICT. |
| Catalog | The products a sales channel or a buyer may see, with prices and stock: GET /v1/catalog on the Channel API, catalog.* on the Store API. |
| Channel binding | The sales channels an API key may write into; empty means all of them. |
channelId | The uuid of a sales channel; every Channel API document carries one. |
| Checkout attempt | One try at paying for a quoted cart: checkout.start, then checkout.status and checkout.confirm. |
| Cursor | The nextCursor of a Channel API list, sent as cursor to read the next page; null on the last page. |
| Document | A Channel API record: customer, product, order, fulfillment order, shipment, invoice, payment, purchase order or vendor. |
| Dry run | X-Dry-Run: true on a Channel API write: it runs in full, answers what it would have produced, and is rolled back. |
ext: address | ext:<channelId>:<externalId>: a Channel API document addressed by the integration's own id. |
externalId | The integration's own id for a document, unique within its sales channel. |
| Fulfillment order | The part of an order one warehouse ships, with its stock reserved there. |
| Fulfillment queue | The orders waiting to ship, with their shippable fulfillment orders. |
| Gateway | Kentro's authentication layer in front of every API; it resolves a credential to a tenant and scopes, or answers 401. |
| Guest token | A Store API token for a shopper without an account, minted by session.guest and sent as X-Storefront-Guest. |
| Historical import | X-Import-Mode: historical: documents stored without confirmation emails, packing slips, accounting exports or EDI documents. |
| Idempotency key | A client-chosen string that makes a retried write answer the first result instead of acting twice. See Errors, retries and rate limits. |
| Kentro GO | Kentro's marketing product: brands, campaigns, landing pages and approvals. Kentro Pixel properties are managed there. |
| Kentro MCP | Kentro's MCP server, which lets AI assistants work with Kentro data as a user, over OAuth. See Kentro MCP. |
| Kentro OS | Kentro's main portal at https://kentro.app (sandbox https://kentro.cc), where API keys, permission groups and storefronts are managed. |
| Kentro Pixel | Kentro's first-party, consent-aware event collection. See Kentro Pixel. |
| Listing | A product's presence on one sales channel, with its price and published state. |
| Location | A place inside a warehouse (a bin) where stock is counted. |
| Lot | A batch of units tracked together, set on inventory levels and shipped lines. |
onDuplicate | What a Channel API create does when the document already exists: update (the default), skip or error. |
| Operation | An asynchronous Channel API job, such as an order import, read at GET /v1/operations/:id. |
outcome | What a Channel API write did: created, updated, skipped, deleted or unchanged. |
| Permission group | A named set of scopes in Kentro OS, assigned to users and API keys. |
| Property | A Kentro Pixel measurement source (a website, a store, a server source) with its own keys and settings. |
| Public key (Pixel) | A pk_live_ or pk_test_ key that the browser SDK sends; visible in page source by design. |
| Purchase order | A retailer's order to the tenant, accepted into a sales order or rejected. |
| Quote | A priced Store API cart (cart.get { "quote": true }) with shipping, tax and quoteFingerprint, valid up to 10 minutes. |
| Request id | The id of one request, in X-Request-Id and the Channel API's requestId; quote it to support. |
| Routing | The tenant's rules that decide which warehouse ships which order lines. |
| Sales channel | A place orders come from: a marketplace, a cart, a B2B storefront, an EDI retailer. |
| Sandbox | Kentro's staging environment for building and testing, on apis.kentro.dev. See Environments. |
| Scope | One permission, such as channel:read, orders:write or storefront:serve. |
| Server key (Pixel) | An sk_ key id and secret that sign Kentro Pixel server events with HMAC-SHA256. |
| Stock review | An order status (stock-review) for orders waiting on a stock decision, accepted or rejected by the tenant. |
| Storefront | A published B2B store on one sales channel; a custom storefront replaces only its rendering. |
| Storefront host | The host buyers use for a storefront, sent as X-Storefront-Host. |
| Tenant | One Kentro account: a business with its users, settings and data. Kentro OS also calls it the workspace. |
updatedSince | The list filter for incremental sync: the latest updatedAt seen so far. |
version | An optimistic-concurrency token on every Channel API document; a stale one answers 409 version_conflict. |
| Warehouse | A building that holds stock and ships orders: the tenant's own, a 3PL's, or the sales channel itself. |
| Workspace | Kentro OS's name for the tenant. |
Updated about 12 hours ago
Did this page help you?