> ## Documentation Index
> Fetch the complete documentation index at: https://nango.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Pushpay ChMS (v2)

> Integrate your application with the Pushpay ChMS REST API (v2)

## 🚀 Quickstart

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

**1. Create the integration**

In Nango ([free signup](https://app.nango.dev)), go to [Integrations](https://app.nango.dev/dev/integrations) -> *Configure New Integration* -> *Pushpay ChMS (v2)*.

Nango doesn't have a Nango-managed 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](https://nango.dev/docs/api-integrations/pushpay-chms-v2/how-to-register-your-own-pushpay-chms-v2-oauth-app). Then add the OAuth client ID, secret, and scopes in the integration settings in Nango.

**2. Authorize Pushpay ChMS**

Go to [Connections](https://app.nango.dev/dev/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.

**3. 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](https://app.nango.dev/dev/environment-settings), [integration ID](https://app.nango.dev/dev/integrations), and [connection ID](https://app.nango.dev/dev/connections):

> [tab] cURL
>
> ```bash theme={null}
> 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>"
> ```

> [tab] Node
>
> Install Nango's backend SDK with `npm i @nangohq/node`. Then run:
>
> ```typescript theme={null}
> 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](https://nango.dev/docs/reference/backend/backend-sdk/node.md#get-a-connection-with-credentials) or [API](https://nango.dev/docs/reference/backend/http-api/connections/get.md).

✅ You're connected! Check the [Logs](https://app.nango.dev/dev/logs) tab in Nango to inspect requests.

**4. Implement Nango in your app**

Follow our [Auth implementation guide](https://nango.dev/docs/guides/primitives/auth.md) to integrate Nango in your app.

To obtain your own credentials, follow the setup guide linked below.

## 📚 Pushpay ChMS (v2) guides

* [How to register your own Pushpay ChMS v2 OAuth app](https://nango.dev/docs/api-integrations/pushpay-chms-v2/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?](https://nango.dev/docs/api-integrations/pushpay-chms-v2/connect)\
  Church subdomain and authorization requirements

Official docs: [Pushpay ChMS API v2 documentation](https://docs.pushpay.io/chms-v2/docs/getting-started)

Official partner form: [Become a value-added partner](https://vendor.ccbchurch.com/goto/forms/12/responses/new)

## 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 tools

Explore Nango-provided tools in your dashboard. Extend and customize them to fit your needs.

*No pre-built syncs or tools available yet.*

> [!TIP]
>
> Not seeing the integration you need? [Build your own](https://nango.dev/docs/guides/functions/functions-guide.md) independently.

***


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.