Connect Cin7: pull orders and customers in, check inventory

In Cin7 Omni at go.cin7.com, open an API connection and note its username and password, fill just those two fields into Integration, test, map and activate — sales orders and customers come in and inventory can be checked.

The Cin7 connector pulls sales orders and customers from Cin7 Omni into this system, and can check inventory quantities held in Cin7, including available and on-hand quantities. It reads from Cin7: it does not push inventory changes back to Cin7, and it does not write orders or customers back to Cin7. There is no address field to set — the connector always uses the official Cin7 API address. One connection uses one API connection from Cin7.

Prerequisites#

• A Cin7 Omni account you can sign in to at go.cin7.com.
• Permission in Cin7 to open or create an API connection. The username and password for this integration come from that API connection.
• The key point before you start: the API username and API password are not your Cin7 sign-in account. Filling in the email and password you use to sign in to Cin7 will not connect.
• Note the Cin7 API rate limits while you plan the pull frequency: 3 requests per second, 60 per minute and 5,000 per day.

Get your credentials#

1. Sign in to Cin7 Omni at go.cin7.com.
2. Open the API connection area and open the API connection you want to use for this integration, or create a new one.
3. Note the username of that API connection. This username is generated for the API connection and is used for Basic authentication — it is not your Cin7 login name.
4. Note the API password set on that same API connection. The username and the password must come from the same API connection — do not mix values from two different connections.

Fill it into Integration#

1. Open Integration → Connector Marketplace → Cin7 → New connection.
2. username — required, Cin7 API username: fill in the username of the API connection from Cin7, for example the username shown on that connection. The hint text in the field reads API username.
3. password — required, Cin7 API password: fill in the API password set on that same API connection. It is a password-type field and is stored as a secret.
4. There is nothing else to fill in. This connection has no address field: it always connects to the official address https://api.cin7.com/api, so do not look for a place to change it.

Test the connection#

Click Test connection. If username or password is missing, the test stops and reports the missing field before sending any request, because Basic authentication needs both values. Otherwise the test sends a Basic-authenticated request to read the branch list, GET https://api.cin7.com/api/v1/Branches — the lightest read in Cin7. A 200 response means the connection works. A 401 response means the credentials are invalid. A 403 response means the credentials were accepted but this API connection has no permission for that resource — 401 and 403 point to different fixes, so read the code before changing anything. The test times out after 12 seconds.

Mapping / pick a template#

Pick the Cin7 standard mapping. Sales orders are read from the Cin7 sales orders data, customers from the Cin7 contacts data, and inventory checks read the Cin7 stock data. After the test passes, run one pull and check a real order side by side — order number, customer, lines and quantities — check one customer record, and check one product quantity against what Cin7 shows, before activating. If a field on your orders differs, adjust that field in the mapping instead of changing records in Cin7.

Activate#

After activation, the connection pulls sales orders and customers from Cin7 into this system on the schedule you set, within the Cin7 rate limits of 3 requests per second, 60 per minute and 5,000 per day, and inventory checks read the current quantities from Cin7. Watch the first pulls in Runs / Logs and compare them with Cin7 before leaving the connection unattended.

What this connection does not do: it does not push inventory changes back to Cin7, and it does not write orders, customers or fulfillment results back to Cin7. Keep handling those in Cin7 itself, or through the other systems where the work actually happens.

FAQ#

Test fails with 401 — credentials invalid

Cin7 rejected the Basic authentication. The username or password does not match an API connection in Cin7 — most often because the Cin7 sign-in email and password were filled in instead, or because the username and password came from two different API connections.

In Cin7 Omni at go.cin7.com, open the API connection, copy its username exactly into the username field, set or copy the API password on that same connection into the password field, save, and test again. Do not use your Cin7 sign-in password.

Test fails with 403 — this API connection has no permission for that resource

This is different from 401: Cin7 accepted the credentials, but the API connection is not allowed to read the branch list used by the test. Changing the password again will not fix a 403.

In Cin7, check the access given to this API connection and allow it to read the resources the connection needs, or switch to an API connection that already has that access. Keep the same username and password pair from that connection, save, and test again.

Test stops before sending a request and reports a missing field

username or password is empty. The test needs both values for Basic authentication, so it stops instead of sending a request that Cin7 can only reject.

Fill in both fields from the same API connection in Cin7 — username from the connection, password set on that same connection — save, and test again.

I filled in my Cin7 sign-in account, but it will not connect

The sign-in account and the API connection credentials are two different things in Cin7. This connection authenticates with the username and password of an API connection only, so a perfectly valid sign-in account still fails here.

Go to go.cin7.com → API connection in Cin7 Omni, open or create an API connection, and use its username and its API password in Integration instead of your sign-in details. Then test again.

Connected, but no sales orders are pulled in

The connection is working — the test read the branch list successfully — but there is nothing new to pull: Cin7 has no new sales orders in the pull range, or the records there are not sales orders.

Create or confirm one sales order in Cin7, then run a manual pull and confirm the order appears in the preview or in Runs / Logs. Keep the pull frequency within the rate limits noted above.

Inventory check returns no quantity for a product

The connection can read stock in Cin7, but that product has no matching stock record to read, or the product code in the mapping does not match the product in Cin7. The test can pass while a single product still has nothing to return.

Check the product and its stock record in Cin7 first, then check the product code for that item in the mapping and correct it to match Cin7. Run the inventory check again for that one product.