Private beta

Ingram Micro Cloud Marketplace support is doc-validated against apidocs.cloud.im but awaiting first-customer onboarding to confirm a real reseller tenant syncs cleanly. Email support to opt in.

Email support@mspvectis.com to request access. The setup steps below describe the intended self-serve flow once the connector exits beta.

What Vectis does with Ingram Micro

Syncs customers and subscriptions from your Cloud Marketplace reseller tenant into customers and license_subscriptions. Customers are fuzzy-matched to PSA rows so license data hangs off the canonical customer hub.
Weekly usage snapshots land in license_usage so seat-count drift is detected on week-scale cadence — same Money Found signal Pax8 + Sherweb produce.
Coexists with Pax8 + Sherweb + TD SYNNEX. Subscriptions are vendor-tagged (vendor='ingram_micro'), so leakage + margin + drift detection work identically whether your MSP uses one distributor or all four.
Read-only. Vectis never writes back to Ingram — subscription changes always go through Cloud Marketplace or your billing flow, not Vectis.

What you’ll need

Client ID and Client Secret from Cloud Marketplace → Settings → API
Subscription Key — the Cloud Marketplace APIM key paired with your OAuth client
Region — your tenant region. Examples: us.na, eu, au. Vectis uses this to build the host name cp.<region>.cloud.im.

1. Mint API credentials

Sign in to your Ingram Cloud Marketplace control panel as a reseller admin.
Open Settings → API. Click Generate new client. Label it “Vectis”.
Copy the client ID, client secret, and subscription key. The secret is shown only once; if you lose it, rotate and regenerate.
Note your tenant region — it’s the sub-domain of the URL you log in with (e.g., cp.us.na.cloud.im → region us.na).

The subscription key is required on every API request — it identifies the reseller tenant your OAuth client is acting on behalf of, the same way Sherweb’s APIM subscription key works.

2. Paste credentials into Vectis

Go to Admin → Integrations and click Configure on Ingram Micro.
Paste the client ID, client secret, subscription key, and region.
Click Test. You’ll see “Connected to Ingram Micro — N subscriptions visible” within a few seconds.
Click Save, then trigger an initial sync.

3. What appears where

Customer hub → Licensing section: per-SKU rollups, cost vs. revenue margins, uncontracted-seat counts. Ingram, Pax8, Sherweb, and Synnex subscriptions render identically in the same table — the vendor column disambiguates.
Licensing-leakage dashboard preset: every customer with uncontracted Ingram seats or below-margin SKUs surfaces here.
Weekly Money Found digest: seat-growth findings + licensing drift events surface in the Monday email.
QBR report: Licensing section vendor label is “Ingram Micro”, “Pax8”, “Sherweb”, “TD SYNNEX”, or “Mixed” depending on which distributor(s) the customer uses.

Common errors

401 Unauthorized — Client ID / secret pair is wrong, or the subscription key is missing / mis-paired. Verify in the control panel.

403 Forbidden — The OAuth client lacks the read scopes for customers + subscriptions, or the subscription key isn’t paired with this client.

404 on /customers or /subscriptions — Region is wrong. The host cp.<region>.cloud.im must resolve to your tenant’s control panel.

429 Too Many Requests — Cloud Marketplace rate limits at ~50 req/min per OAuth client. The ETL paces below that; if you see 429s, another tool is likely sharing the credential — mint a dedicated one for Vectis.