SaaS distribution integration
Sherweb SaaS license inventory joins Pax8 on the same leakage + margin surface — especially useful for MSPs in Canada + France.
In Beta
Vectis + Sherweb is in Beta. We built this connector against Sherweb’s published API documentation (verified endpoints in scripts/audit/known-endpoints/sherweb.json). It’s fully connectable today — credentials save and syncs run. Because Sherweb 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 Sherweb and want to be the validator, talk to us.
What Vectis syncs
Sherweb customer mappings sync per partner tenant on first run, and from there Vectis pulls every subscription with SKU, quantity, cost, and term. Subscription rows are vendor-tagged so cross-distributor reconciliation against Pax8, Ingram Micro, and TD SYNNEX is identical — the same leakage preset and Money Found digest treat all four sources the same way.
What you can do
Sherweb is a read-only adapter here — Vectis surfaces subscriptions and feeds them into rules, but provisioning and subscription changes happen inside the Sherweb Partner Portal. The value lands in cross-distributor leakage detection: M365 seats billed via Sherweb sit in the same license_subscriptions table as seats billed via Pax8, so uncontracted or below-margin shows up regardless of which distributor issued the invoice.
Honest about the limits
Beta — the HTTP client was rewritten under Phase 142 against Sherweb's documented OAuth and REST surface (endpoints verified in scripts/audit/known-endpoints/sherweb.json) and is awaiting first-customer validation before flipping to general availability. Sherweb doesn't offer a public sandbox, so the first paying MSP to connect is the de-facto live validator. The adapter stays read-only by deliberate scope — provisioning and subscription changes belong in the Sherweb Partner Portal, with the result reflected back via the next sync.
How it correlates
Sherweb on the customer account hub alongside every other system you run — not a standalone dashboard. A few of the most common shapes this takes:
Sherweb-sourced M365 subscriptions and Pax8-sourced M365 subscriptions land in the same license_subscriptions table, vendor-tagged. The Licensing-leakage preset and Money Found digest treat them identically — uncontracted or below-margin shows up regardless of which distributor billed it.
If a customer's M365 seat count drifts between the Sherweb subscription and the PSA contract line, Vectis flags it. Works the same way across Pax8, Sherweb, Ingram Micro, and TD SYNNEX.
Setup snapshot
In the Sherweb Partner Portal, open API Credentials and create a dedicated OAuth client for Vectis so credential rotations only affect this integration. Paste the Client ID, Client Secret, and your partner tenant ID into Vectis; leave scope blank for the default read-only service scope unless your partner agreement narrows it. Vectis tests against the subscriptions endpoint before saving so a bad credential or wrong tenant ID fails fast. The first sync pulls customers and subscriptions end-to-end; subsequent syncs run incrementally on a schedule.
# In the Vectis hub, add the connector:
category SaaS distribution
vendor Sherweb
status Read-onlyOther SaaS distribution integrations
Pricing
Sherweb is available on every Vectis tier — $299/mo and up. See pricing
Also reachable over MCP — bring your own client → /mcp
