Your orientation to the Virtuous API Docs — the four tabs, the consistent group structure within each, and how to find what you need by use case
These Virtuous API Docs document the three Virtuous APIs - CRM+, Raise, and Volunteer - plus a platform-wide Virtuous tab that covers content cutting across all three. The docs are designed for partners and engineers building integrations, but they’re also useful for anyone evaluating or working with the Virtuous platform.This page is your orientation: what’s where, how the content is organized, and how to find what you need.
Each of the three product tabs (CRM+, Raise, Volunteer) follows the same group structure, so once you learn one, you can navigate the others. The groups, in the order they appear:
Group
What’s there
When to read
Get Started
Authentication, base URLs, your first API call, error handling, rate limits, pagination
Starting a new integration; coming back to refresh basics
Core Concepts
The data model, major resources, and how they relate
Designing an integration; understanding what data looks like before you write code
Common Workflows
Task-oriented walkthroughs (create a contact, sync donations, manage groups, etc.)
When you have a specific task to accomplish
Webhooks (CRM+, Raise) or Polling and Sync (Volunteer)
Change detection — webhooks where supported, polling patterns where webhooks aren’t available
When you need to react to data changes, not just read snapshots
Integration Recipes
End-to-end opinionated implementations of common partner integrations
When you’re building something that maps to a recognized pattern
When you’re operationalizing — turning a working integration into a production-grade one
The progression matters: Get Started → Concepts → Workflows → Webhooks/Polling → Recipes → Best Practices is also roughly the order in which you’ll need them as you build.
The product tab Overview pages and the Get Started groups are the natural front doors. The docs are also navigable linearly within each group — every page ends with a CardGroup pointing to natural next reads.
The docs are continuously updated. Things to know:
Practice
Detail
Continuous publishing
New content and updates appear on the live site as they’re published — no version waits
Recent additions
Partner program documentation, MCP server, and these Docs Guide pages are recent additions to the platform tab
API evolution
As CRM+, Raise, and Volunteer evolve, the docs evolve with them. The Best Practices pages cover Versioning and Backward Compatibility — patterns for keeping integrations resilient through API changes
Audit-driven cleanup
A continuous audit pass surfaces and fixes spec gaps, naming inconsistencies, and documentation completeness issues
