n-Cin7 Has a Real API. Most of the Work Is What You Build With It.
Cin7's REST API lets an outside system read and write inventory levels, sales orders, purchase orders, and warehouse transfers without anyone opening the Cin7 interface by hand, the same API Cin7's own app marketplace connectors are built on. Cin7 Core (the former DEAR Systems product) and Cin7 Omni each expose their own version of it, so the exact endpoints and authentication differ a little depending which one you're running. We build directly against whichever one you're on, to connect Cin7 to the EDI feeds, 3PL warehouses, B2B portals, and CRMs its own marketplace doesn't already handle.
What the Cin7 API actually covers
Inventory and order data, in both directions. Stock levels, sales orders, purchase orders, and warehouse transfers can all be read out or written in through the API, which is how a third-party channel, a 3PL, or a custom reporting tool stays in step with what Cin7 actually has on hand.
The same API powers EDI, 3PL, and B2B connections. When a big retail customer wants orders delivered through an EDI feed, when a 3PL needs stock and shipment data flowing both ways, or when a wholesale B2B portal needs to check live inventory before a buyer checks out, it's this API doing the work underneath, whether that connection ships as a listed marketplace app or gets built directly against the endpoints for a setup that's more specific than the standard case.
CRM and warehouse management data too. A CRM that needs order history for a sales rep, or a warehouse management workflow Cin7's own WMS module doesn't quite cover, both come down to the same API calls, just aimed at a different system on the other end.
Where the API runs out and a build starts
The API itself is comprehensive enough for genuine custom work. What it doesn't give you is a connector that already exists for your specific combination of systems, and for a niche 3PL, an in-house B2B portal, or a CRM without a Cin7 listing, that connector has to be built rather than installed.
Every so often the system on the other end is the real constraint, an older EDI value-added network, a supplier portal with no API at all, something that predates having one. When that's the actual limitation, we build against that system's screens directly with headless-browser automation instead of waiting on an API that isn't coming, and still land the data in Cin7 through its own API on the other side.
What we build with Cin7's API
EDI orders landing as real Cin7 sales orders
A retail customer's EDI feed turns into a properly formed Cin7 sales order automatically, checked against live stock before it's confirmed back, instead of someone retyping a purchase order from an EDI document by hand.
A 3PL or B2B portal that actually matches Cin7
Stock and shipment data move both ways between Cin7 and a 3PL or wholesale portal in near real time, so a buyer never sees availability that's already gone stale by the time they check out.
Which system still isn't talking to Cin7?
An EDI customer, a 3PL, a CRM, a portal with no listed Cin7 app, tell us which one and we'll look at what building it directly actually takes.
Still exporting or re-keying data between Cin7 and a system its marketplace doesn't cover?
Tell us which system it is, a 3PL, an EDI customer, a CRM, a portal, and what's moving between the two by hand right now. Cin7's API is just the example here; we build the same kind of connection against whatever your business actually runs.
Let's talk