How to Get Your Cin7 API Key (and What to Build With It)

How Cin7 API access works

Cin7 uses an API account identifier and application key created inside Cin7. The exact screens move around as Cin7 updates its interface, so rather than repeat a menu path that may already be out of date, the reliable source is the official documentation: Cin7 developer documentation.

Cin7 Core, previously DEAR Systems, and Cin7 Omni are separate products with separate APIs. Confirm which one you are on before starting, because the endpoints differ.

What the Cin7 API lets you do

The Cin7 API gives you programmatic access to the core data in your account. Broadly that covers:

• Products, families and stock levels
• Sales orders, invoices and credit notes
• Purchase orders and supplier records
• Customers, contacts and price tiers
• Warehouses, bins and stock transfers
• Bill of materials and production orders

With that access you can push data into accounting or reporting systems, keep records in step across tools, and build dashboards from live Cin7 data rather than from exports someone has to remember to run.

Cin7 and no-code tools

Zapier support for Cin7 is limited. Zapier coverage is limited, and most Cin7 work uses the API directly. That is why searches for connecting Cin7 through no-code tools tend to turn up workarounds rather than a clean answer.

Building with the Cin7 API

Connecting Cin7 to another system means working through five things, in roughly this order:

1. Authenticate using the credentials above, and store them somewhere your team can rotate
2. Map the data, deciding what moves between Cin7 and the other system, in which direction, and triggered by what
3. Handle the edge cases, such as a record that already exists on one side but not the other, or a partially completed transaction
4. Build error handling, so a failed call is retried or surfaced rather than silently dropped
5. Set up monitoring, so you find out something stopped working before it becomes an accounting problem

A common pairing is Cin7 with Xero or Shopify. Read-only reporting is usually straightforward. Live two-way sync is where the mapping and error handling turn it into a proper development project.

When to bring in a developer

Some Cin7 API work is genuinely straightforward. Some is not. An honest split:

These integrations look simple from the outside. The work is in the detail: field mapping, conflict resolution, error recovery, and keeping everything in step as both Cin7 and the connected system change over time.

If the integration touches invoicing, stock or payroll, getting it wrong has real financial consequences. A properly built integration with monitoring and alerting is worth the upfront cost.