What you'll need
- Site URL — the regional endpoint, e.g.
https://na.myconnectwise.net - Company ID — your short company identifier (not the full company name)
- Public key + Private key — issued per API member
- Client ID — a developer-registered GUID from the Developer Portal
1. Create an API member
- In ConnectWise, go to System → Members → API Members.
- Click New. Fill in the required member fields. Role: pick a role with the minimum permissions needed (service tickets, companies, contracts, time entries — no billing unless you want invoices synced).
- Save. You now have an API member but not yet a key.
2. Generate the public/private key pair
- On the API member you just created, open the API Keys tab.
- Click New and give the key a description like “Vectis”.
- Save. The private key is shown only once — copy it immediately. The public key is always visible.
3. Register a developer client ID
ConnectWise rejects API calls from unregistered client apps with a 400 and “clientId” in the error. You need one registered client ID; reuse it across all your integrations.
- Go to
https://developer.connectwise.comand sign in. - Navigate to My Clients and register a new client. Description: “Vectis”. Accept the terms.
- Copy the resulting GUID — that’s your Client ID.
4. Paste credentials into Vectis
- Go to Admin → Integrations and click Configure on ConnectWise.
- Paste all five values. The Site URL must include the protocol and no trailing slash.
- Click Test. You should see “Connected to ConnectWise” within a few seconds.
- Click Save, then Sync now.
Common errors
401 Unauthorized — Company ID, public key, or private key is wrong. Company ID is case-sensitive and is your short identifier, not the company’s display name.
403 Forbidden — The API member’s role lacks permission for the endpoint. Check the role has read access to Service Tickets, Companies, and the Member’s home system.
400 with “clientid” — Client ID wasn’t registered at the developer portal (step 3). Register a client ID and paste the GUID.
Connection timed out — Wrong Site URL (e.g. typoed region) or ConnectWise Cloud is down. Try opening the Site URL in a browser to verify.