Pushpay ChMS (v2)

🚀 Quickstart

Connect to the Pushpay ChMS v2 API with Nango using OAuth 2.0 (System Auth).

Create the integration

In Nango (free signup), go to Integrations -> Configure New Integration -> Pushpay ChMS (v2).Nango doesn’t provide a test OAuth app for Pushpay ChMS v2. You’ll need to register as a value-added partner and create your own OAuth application by following the setup guide. Then add the OAuth client ID, secret, and scopes in the integration settings in Nango.

Authorize Pushpay ChMS

Go to Connections -> Add Test Connection -> Authorize, enter the church subdomain, then complete the Pushpay ChMS authorization prompt as a Master Administrator (or a user who can edit system-wide settings). Later, you’ll let your users do the same directly from your app.

Call the Pushpay ChMS API

Let’s make your first request to the Pushpay ChMS v2 API (GET /individuals). Replace the placeholders below with your API key, integration ID, and connection ID:

cURL
Node

curl "https://api.nango.dev/proxy/individuals?per_page=1" \
  -H "Authorization: Bearer <NANGO-API-KEY>" \
  -H "Provider-Config-Key: <INTEGRATION-ID>" \
  -H "Connection-Id: <CONNECTION-ID>"

Install Nango’s backend SDK with npm i @nangohq/node. Then run:

import { Nango } from '@nangohq/node';

const nango = new Nango({ secretKey: '<NANGO-API-KEY>' });

const res = await nango.get({
    endpoint: '/individuals',
    params: { per_page: 1 },
    providerConfigKey: '<INTEGRATION-ID>',
    connectionId: '<CONNECTION-ID>'
});

console.log(res.data);

Or fetch credentials dynamically via the Node SDK or API.✅ You’re connected! Check the Logs tab in Nango to inspect requests.

Implement Nango in your app

Follow our Auth implementation guide to integrate Nango in your app.To obtain your own production credentials, follow the setup guide linked below.

📚 Pushpay ChMS (v2) guides

How to register your own Pushpay ChMS v2 OAuth app
Become a partner and obtain OAuth client credentials for System Auth
How do I link my Pushpay ChMS account?
Church subdomain and authorization requirements

Official docs: Pushpay ChMS API v2 documentation Official partner form: Become a value-added partner

API notes

All API calls use https://api.ccbchurch.com (not https://{subdomain}.ccbchurch.com).
This integration uses System Auth (church administrator authorizes your vendor app). Identity Auth (resource_owner_auth) is a separate flow for acting as an individual after System Auth is already granted.

🧩 Pre-built syncs and actions

Enable them in your dashboard. Extend and customize to fit your needs. No pre-built syncs or actions available yet.

Not seeing the integration you need? Build your own independently.

⌘I

Overview

900+ APIs & Integrations

🚀 Quickstart

📚 Pushpay ChMS (v2) guides

API notes

🧩 Pre-built syncs and actions

​🚀 Quickstart

​📚 Pushpay ChMS (v2) guides

​API notes

​🧩 Pre-built syncs and actions

🚀 Quickstart

📚 Pushpay ChMS (v2) guides

API notes

🧩 Pre-built syncs and actions