Skip to main content
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.

The Four Tabs

The top-level navigation has four tabs: Each product tab is self-contained for its API. The Virtuous tab is for content that applies to the platform as a whole.

The group structure within each product tab

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: 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 Virtuous tab

The Virtuous tab holds content that applies platform-wide: If you’re new to Virtuous and building integrations, the Integration Pathway in the Partners group is the canonical workflow for technology partners.

How to find what you need

The right starting point depends on what you’re trying to do:

“I’m starting fresh — what do I need to know?”

  1. Start with Becoming a Partner if you’re not yet in the program
  2. Pick the relevant product tab (CRM+, Raise, or Volunteer)
  3. Read the Get Started group in order — it gives you the foundational concepts
  4. Move to Core Concepts to understand the data model before writing code

”I know what I’m building — show me the pattern”

  1. Go directly to the relevant product’s Integration Recipes group
  2. Find the recipe closest to what you’re building
  3. Use the recipe as your reference; cross-link into Workflows and Concepts as needed

”I have a specific task to accomplish”

  1. Go to the relevant product’s Common Workflows group
  2. Find the workflow that matches your task
  3. Each workflow is self-contained with code examples

”Something specific isn’t working”

  1. Use Search (Cmd+K) to find the relevant page
  2. Or ask the AI Assistant — it can pull from across the docs
  3. The Best Practices pages cover most production-grade concerns

”I’m working in an AI tool while I build”

  1. The AI Assistant is built into the docs site — open it with Cmd+I
  2. For your external AI tools (Cursor, Claude Code, VS Code, etc.), connect them to the MCP server so they can query these docs as you work

”I just want to read”

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.

Conventions across the docs

A few things you’ll see consistently:

How the docs evolve

The docs are continuously updated. Things to know:

Where to go next

Search and Navigation

Finding what you need fast — the search bar, keyboard shortcuts, and cross-link patterns.

AI Assistant

The in-docs AI chat — ask questions, get cited answers, and skip the hunt-and-peck.

Contextual Menu

Copy pages, open them in ChatGPT or Claude, and pull docs into your AI tool of choice.

API Playground

Test endpoints directly in the browser and copy the resulting code into your project.
Last modified on May 22, 2026