The API Report CardAPI Index
Vitally

Vitally API

Customer Success Platform (CSP) for B2B SaaS · vitally.io

Two self-serve, documented APIs at docs.vitally.io: a REST API for CRUD on accounts, users, tasks, and custom objects, and an Analytics API for product event ingestion. Keys come from Settings with a documented 1,000 req/min limit. The gaps: no official SDKs and no outbound webhooks.

Last verified: July 2026Marketing & Sales
API GRADE
D+
VERIFIED JUL 2026

SCORECARD

ExistenceGOODTwo public APIs documented at docs.vitally.io, a REST API for CRUD and an Analytics API for event ingestion, with self-serve keys.
AccessGOODSelf-serve: the API key is generated in Settings, with a documented 1,000 req/min sliding-window limit.
CoverageGOODCRUD across accounts, users, conversations, notes, tasks, projects, and custom objects, plus event ingestion via the Analytics API.
AuthPOORBasic Auth with the API key as username; no OAuth, scopes, or per-integration tokens.
Docs & DXPOORNo first-party SDKs and no outbound webhooks; bulk operations are documented only as Postman recipes.
StabilityMIXED
Supergood: Vitally has an API, but using it means gates, contracts, or workarounds. Ours doesn't: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

Vitally scores D+ on the API Report Card. Two self-serve, documented APIs at docs.vitally.io: a REST API for CRUD on accounts, users, tasks, and custom objects, and an Analytics API for product event ingestion. Keys come from Settings with a documented 1,000 req/min limit. The gaps: no official SDKs and no outbound webhooks.

Tried to integrate with Vitally?
SOURCES
No outbound webhooks documented in the public REST API surface, integrators must poll or rely on inbound push patterns docs.vitally.io
No native SCIM 2.0 endpoint and no IdP-native SCIM provisioning documented, IT/identity teams must script via REST stitchflow.com
No first-party SDKs in Python, Node, Go, or Ruby, only a third-party Postman collection is publicly available postman.com
Bulk operations only documented as Postman recipes (POST/PUT/DELETE bulk) rather than first-class batch endpoints docs.vitally.io
Auto-creation of custom trait keys on write produces schema sprawl across the identity graph over time; no enforced trait registry stitchflow.com
User deletion via API is permanent and removes associated event history; no soft-delete or deactivation state exposed stitchflow.com
Each user upsert is individual at scale, developers must parallelize carefully while respecting the 1,000 req/min sliding window docs.vitally.io
Basic Auth with a single API key (no OAuth 2.0, no scoped tokens) complicates multi-tenant SaaS integrations and credential rotation docs.vitally.io
Analytics API and REST API are architecturally separate with different auth and write models, integrators must learn both docs.vitally.io
Initial setup of dashboards, playbooks, and integrations is not intuitive and requires meaningful upfront planning g2.com
Onboarding experience flagged by some reviewers as poor post-sale, with perceived gap between sales promise and implementation support g2.com
Per-seat + per-viewer pricing is perceived as high relative to seats included; cost scales painfully with team size vendr.com
Annual contract spread is wide and quote-based: $18K-$45K (SMB), $40K-$80K (mid-market), $75K-$200K+ (enterprise) with $2K-$10K+ implementation fees vendr.com
Account tracking rules are limited in flexibility, requiring workarounds for non-standard customer hierarchies g2.com
Some areas of the UI require navigation effort despite the platform's modern design reputation g2.com
Reporting depth, while improving, still pushes power users to export to BI tools (Looker, Snowflake) for advanced cohort analysis capterra.com
Many platform integrations are listed as 'Coming soon' on the integrations page, gating deployment timelines vitally.io