SaaS distribution integration
Ingram Micro Cloud Marketplace license inventory on the same leakage + margin surface as every other distributor.
In Beta
Vectis + Ingram Micro is in Beta. We built this connector against Ingram Micro’s published API documentation (verified endpoints in scripts/audit/known-endpoints/ingram-micro.json). It’s fully connectable today — credentials save and syncs run. Because Ingram Micro doesn’t offer a public sandbox for us to live-test against, the first paying customer who connects it is the de-facto live validator. If you’re considering Vectis with Ingram Micro and want to be the validator, talk to us.
What Vectis syncs
Ingram Micro Cloud Marketplace reseller-tenant customer mappings sync on first run, and from there Vectis pulls subscriptions with SKU, quantity, cost, and term. License rows are vendor-tagged so cross-distributor reconciliation against Pax8, Sherweb, and TD SYNNEX uses the same leakage and margin surface — one table, one digest, regardless of which reseller program billed the seat.
What you can do
Ingram Micro is a read-only adapter here — Vectis surfaces subscriptions and feeds them into rules, but provisioning and subscription changes happen inside Cloud Marketplace. The value lands in cross-distributor leakage detection: Microsoft CSP and security SaaS billed through Ingram sit in the same license_subscriptions table as the equivalents billed through Pax8 or Sherweb, so margin drift and uncontracted seats surface regardless of source.
Honest about the limits
Beta — the Cloud Marketplace adapter is built against the documented OAuth 2.0 and REST surface at apidocs.cloud.im (endpoints verified in scripts/audit/known-endpoints/ingram-micro.json) and is awaiting first-customer validation before flipping to general availability. Cloud Marketplace runs regional control-panel hosts (cp.us.na.cloud.im, cp.eu.cloud.im, cp.au.cloud.im, etc.), so the adapter carries a region code per connection — multi-region MSPs wire one connection per operating tenant, and data merges into one account hub per customer.
How it correlates
Ingram Micro on the customer account hub alongside every other system you run — not a standalone dashboard. A few of the most common shapes this takes:
Ingram-sourced Microsoft CSP and security SaaS join Pax8 + Sherweb + SYNNEX in one license_subscriptions table. One leakage dashboard, one weekly digest, regardless of which reseller program billed the seat.
Cloud Marketplace runs regional control-panel hosts (cp.us.na.cloud.im, cp.eu.cloud.im, cp.au.cloud.im, …). The adapter carries a region code per connection so a multi-region MSP wires one connection per operating tenant — the data still merges into one account hub per customer.
Setup snapshot
In Cloud Marketplace, open Settings → API and mint an OAuth 2.0 client (Client ID and Client Secret) plus an APIM subscription key. Paste the Client ID, Client Secret, the subscription key, and your tenant region (us.na, eu, au, etc.) into Vectis; the adapter builds the host as cp.{region}.cloud.im. The region must match your operating tenant — multi-region MSPs wire one connection per region. Vectis tests with a subscriptions query before saving so a wrong-region or bad-credentials configuration fails fast.
# In the Vectis hub, add the connector:
category SaaS distribution
vendor Ingram Micro
status Read-onlyPricing
Ingram Micro is available on every Vectis tier — $299/mo and up. See pricing
Also reachable over MCP — bring your own client → /mcp
