# Cin7 Omni setup for PopMCP

You end up with your Cin7 Omni API Username and the API Key of one API v1 connection, which PopMCP sends together as HTTP Basic auth.

- Auth: API credentials
- Setup time: 6 min
- API base URL: https://api.cin7.com/api/v1
- Credentials screen: https://go.cin7.com/Cloud/
- Provider docs: https://help.omni.cin7.com/hc/en-us/articles/10015165519503-Set-up-a-Cin7-Omni-API-connection

## Before you begin

- A Cin7 Omni account. This is the legacy Omni product, not Cin7 Core (formerly DEAR), which uses different credentials
- An administrator user. The Integrations & API settings are admin-only
- A free API connection slot. Cin7 caps how many connections a site may have and only support can raise it

## Get your credentials

### 1. Sign in to Cin7 Omni as an administrator

Sign in at go.cin7.com with an administrator account.

Screen: https://go.cin7.com/Cloud/

### 2. Open Settings, then Integrations & API, then API v1

Open Settings from the user menu in the top navigation, then under Integrations & API select API v1. Copy the API Username printed at the top of the page.

### 3. Add a new API connection and copy the key

Click Add New API Connection, enter an App Name such as `PopMCP`, and save. Copy the API Key from the confirmation before you close it.

### 4. Tick the permissions the connection needs

Open Permissions under the API Connections list, tick read and write for every module the AI should touch, then click Save.

### 5. Paste both values into PopMCP

Enter the API Username from step 2 and the API Key from step 3 into PopMCP.

## Fields PopMCP asks for

- API Username (apiUsername) [required]: Cin7 Omni → Settings → Integrations & API → API v1 → Add New API Connection. Copy the API Username shown for the new connection.
- API Key (apiKey) [required]: The API Key shown for that same connection. Stored encrypted; Cin7 shows it once.

## Verify

PopMCP shows the Cin7 Omni connection as Connected and a product or stock listing tool returns items from your Cin7 catalogue.

## Troubleshooting

### 401 Unauthorized

Cause: The API Username and API Key are mismatched, or the key was regenerated after you copied it.

Fix: Recheck the username on the API v1 page and regenerate the connection key, then reconnect with the fresh pair.

### 403 mentioning a resource such as Branches

Cause: That module is unticked in the connection's Permissions.

Fix: Open Permissions under API Connections, tick the module, click Save, and retry.

### "Unable to create more than X API connections"

Cause: The account has used all of its allotted connection slots.

Fix: Delete an unused connection, or ask Cin7 Omni support to add the new one for you.

### Credentials rejected and your account looks nothing like the screens above

Cause: You are on Cin7 Core, formerly DEAR, which uses an Account ID and Application Key instead.

Fix: Use the Cin7 Core connector, not this one.

### 429 Too Many Requests

Cause: You exceeded 3 calls a second, 60 a minute or 5,000 a day.

Fix: Slow the tool calls down and prefer filtered queries on modified date instead of full listings.

---

Source: https://www.docs.popmcp.com/docs/integrations/cin7/