Datasource Background Check Partner API documentation

Order and track background checks for the churches you serve. Connect a church once (on a page we host, or with POST /clients), then order checks by applicant name and email; we email the applicant for their details and consent, and send you signed webhooks as checks progress. REST + JSON, API key auth. You never handle SSNs, dates of birth, card numbers or passwords.

• Integration guide: concepts, every flow end to end, code samples, limits
• API reference: every operation and webhook, with fields and JSON examples
• Error catalog: every code, its HTTP status, and whether a retry is safe
• Changelog: dated API changes
• Interactive reference: try requests in the browser
• OpenAPI 3.1 document: the machine-readable reference
• Postman collection: every request and error example, ready to run against the sandbox
• llms.txt and llms-full.txt: these docs as plain text for AI agents

Environments

Use with AI coding agents (MCP)

Our remote MCP server lets AI coding agents (Claude Code, Cursor and other MCP clients) read these docs while you build your integration, and try the sandbox with your test key. It uses the Streamable HTTP transport.

• https://partners.cbgc.io/mcp: the docs tools (list_operations, get_operation, search_docs, get_error, list_webhooks, get_webhook, get_guide_section). No key needed. Production never offers ordering tools.
• https://dev.partners.cbgc.io/mcp: the docs tools, plus sandbox tools (get_settings, list_products, list_clients, order_check, get_check, list_checks, simulate_check) when you send your pk_test_ key as X-Api-Key (or Authorization: Bearer). They follow the same rules as the API. Live keys (pk_live_) are refused.

Claude Code:

claude mcp add --transport http datasource https://partners.cbgc.io/mcp
claude mcp add --transport http datasource-sandbox https://dev.partners.cbgc.io/mcp --header "X-Api-Key: $DATASOURCE_TEST_KEY"

Cursor (.cursor/mcp.json):

{
  "mcpServers": {
    "datasource": { "url": "https://partners.cbgc.io/mcp" },
    "datasource-sandbox": {
      "url": "https://dev.partners.cbgc.io/mcp",
      "headers": { "X-Api-Key": "${env:DATASOURCE_TEST_KEY}" }
    }
  }
}

Keep the key in an environment variable (DATASOURCE_TEST_KEY above), not in a file you commit. Sandbox checks are not real: use made-up applicants, never a real person's details.