> ## 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 (v1)

> Integrate your application with the Pushpay ChMS XML API (v1)

## 🚀 Quickstart

Connect to the Pushpay ChMS API through Nango using HTTP Basic Authentication and your organization subdomain.

<Steps>
  <Step title="Create an integration">
    In Nango ([free signup](https://app.nango.dev)), go to [Integrations](https://app.nango.dev/dev/integrations) -> *Configure New Integration* -> *Pushpay ChMS (v1)*.
  </Step>

  <Step title="Authorize Pushpay ChMS">
    Go to [Connections](https://app.nango.dev/dev/connections) -> *Add Test Connection* -> *Authorize*, then enter your church subdomain, API username, and API password (see the connect guide below). Later, you'll let your users do the same directly from your app.
  </Step>

  <Step title="Call the Pushpay ChMS API">
    Let's make your first request to the Pushpay ChMS API (`api_status` service). Replace the placeholders below with your [secret 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):

    <Tabs>
      <Tab title="cURL">
        ```bash theme={null}
        curl "https://api.nango.dev/proxy/api.php?srv=api_status" \
          -H "Authorization: Bearer <NANGO-API-KEY>" \
          -H "Provider-Config-Key: <INTEGRATION-ID>" \
          -H "Connection-Id: <CONNECTION-ID>"
        ```
      </Tab>

      <Tab title="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: '/api.php?srv=api_status',
            providerConfigKey: '<INTEGRATION-ID>',
            connectionId: '<CONNECTION-ID>'
        });

        console.log(res.data);
        ```
      </Tab>
    </Tabs>

    Or fetch credentials dynamically via the [Node SDK](/reference/sdks/node#get-a-connection-with-credentials) or [API](/reference/api/connection/get).

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

  <Step title="Implement Nango in your app">
    Follow our [Auth implementation guide](/guides/primitives/auth) to integrate Nango in your app.

    To obtain your own production credentials, follow the setup guide linked below.
  </Step>
</Steps>

## 📚 Pushpay ChMS (v1) guides

* [How do I link my Pushpay ChMS account?](/api-integrations/pushpay-chms-v1/connect)\
  Subdomain, API user, and permissions in Pushpay ChMS

Official implementer guide: [Pushpay ChMS API documentation](https://designccb.s3.amazonaws.com/helpdesk/files/official_docs/api.html)

Support article: [How to create and manage API users in ChMS](https://support.pushpay.com/s/article/How-to-Create-and-Manage-API-Users)

## API notes

* Responses are **XML**; Nango forwards the raw body from the proxy.
* Optional `describe_api=1` on any service returns accepted parameters without counting against your daily quota.
* Rate limits: monitor `X-RateLimit-*` headers; on HTTP `429`, honor `Retry-After`. There is also a separate **daily** limit per API user; `api_status` reports usage and does not increment the counter.

## 🧩 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.*

<Tip>Not seeing the integration you need? [Build your own](/guides/functions/functions-guide) independently.</Tip>

***