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.

​

Overview

1. Church subdomain — the hostname prefix for your ChMS site (https://{subdomain}.ccbchurch.com).
2. API username — created in API Admin inside Pushpay ChMS (not the API User Community login).
3. API password — the password for the API user created in API Admin.

​

Prerequisites:

• You must have a Pushpay ChMS account with API access enabled for your organization.

​

Instructions:

​

Step 1: Finding your Church subdomain

1. Log in to Pushpay ChMS as an administrator.
2. Open API Admin (location may vary by version; your implementer guide references this section).
3. Note the HTTPS base URL for API calls. It is of the form https://{your-subdomain}.ccbchurch.com/api.php.
4. The value before .ccbchurch.com is your Church subdomain (for example, acme from https://acme.ccbchurch.com).

​

Step 2: Create an API user

1. In Pushpay ChMS, go to API Admin.
2. Create a dedicated API login for this integration (recommended so access can be revoked independently).
3. Assign only the services this integration needs; each login’s permissions are granular per service.
4. Copy the username and password for use in Nango.

​

Step 3: Enter credentials in the Connect UI

1. Open the form where you need to authenticate with Pushpay ChMS.
2. Enter your Church subdomain, API Username, and API Password in their respective fields.
3. Submit the form, and you should be successfully authenticated.