Connect vendor admin APIs for usage and seat data
Per-vendor admin API connections add seat and usage data that powers rightsizing, renewal prep, and seat-drift findings.
Why connect vendor admin APIs
Identity providers tell Cubbie who has access; vendor admin APIs tell Cubbie what is actually happening inside each product — seats purchased, seats active, last activity. These per-vendor connections power the most precise rightsizing features: dormant-seat hints in renewal prep, seat-drift findings, and per-subscription utilization pages.
Browse the catalog
1. Open Integrations → Vendors in your dashboard.
2. Search the catalog or filter by category. Cubbie maintains admin-API integrations for well over one hundred SaaS vendors, and the list keeps growing.
3. Vendors that are available now show a Connect action. Vendors not yet wired up show a Request priority action — requesting records your interest and directly influences which vendor Cubbie builds next.
Connect a vendor
Each vendor has its own connect flow; most use an admin OAuth grant or an API key created in that vendor admin console. The connect page for each vendor walks through the exact steps and shows the permissions requested. Connections are scoped to reading usage and seat data for rightsizing — not to managing the product.
Where the data shows up
- Seat utilization: per-subscription pages compare licensed seats against active users.
- Renewal prep: the dormant-seat hint on the renewal calendar uses this signal to recommend the right ask in your next negotiation.
- Seat drift: over-provisioning findings get sharper when real activity data backs them.
Manage connections
The Connections page lists every live connection with its provider, status, and last sync result, so stale or failing connections are easy to spot and fix.
Start with your five most expensive vendors — that is where dormant seats hide the most money.