Skip to main content

🚀 Quickstart

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

Create an integration

In Nango (free signup), go to Integrations -> Configure New Integration -> Pushpay ChMS (v1).
2

Authorize Pushpay ChMS

Go to 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.
3

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, integration ID, and connection ID:
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>"
Or fetch credentials dynamically via the Node SDK or API.✅ You’re connected! Check the Logs tab in Nango to inspect requests.
4

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

Official implementer guide: Pushpay ChMS API documentation Support article: How to create and manage API users in ChMS

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.
Not seeing the integration you need? Build your own independently.