The API Report CardAPI Index
Cin7

Cin7 API

Inventory Management / Order Management / SMB-to-Mid-Market · cin7.com

Cin7 ships two separate REST APIs, Core (formerly DEAR) and Omni, each with its own portal, auth model, and endpoint set. Both use static key pairs generated in-app rather than OAuth. Coverage spans products, orders, and stock with webhooks, but rate-limit caps are unpublished.

Last verified: July 2026Retail & Ecommerce
API GRADE
D
VERIFIED JUL 2026

SCORECARD

ExistenceGOODTwo documented REST APIs: Core (formerly DEAR) and Omni, each with its own portal, endpoints, and webhook support.
AccessGOODSelf-serve key generation inside both Core and Omni for paying customers, with public docs and no partner gate.
CoverageGOODCore API spans products, sales, purchases, stock, BOMs, payments, and contacts with webhooks; Omni covers its own parallel surface.
AuthPOORStatic key pairs on both APIs: Core sends account and application keys in headers, Omni uses HTTP Basic; no OAuth.
Docs & DXPOORDocs split across two brand-distinct portals; the Core reference still lives on Apiary and omits rate-limit numbers.
StabilityMIXEDCore runs legacy v1 and current v2 with a recent-changes log, but rate caps are unpublished and found empirically.
Supergood: Cin7 has an API, but using it means gates, contracts, or workarounds. Ours doesn't: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

Cin7 scores D on the API Report Card. Cin7 ships two separate REST APIs, Core (formerly DEAR) and Omni, each with its own portal, auth model, and endpoint set. Both use static key pairs generated in-app rather than OAuth. Coverage spans products, orders, and stock with webhooks, but rate-limit caps are unpublished.

Tried to integrate with Cin7?