Pushpay ChMS (v1)
Integrate your application with the Pushpay ChMS XML API (v1)
🚀 Quickstart
Connect to the Pushpay ChMS API through Tenklo using HTTP Basic Authentication and your organization subdomain.
In Tenklo (free signup), go to Integrations -> Configure New Integration -> Pushpay ChMS (v1).
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.
Let's make your first request to the Pushpay ChMS API (api_status service). Replace the placeholders below with your Environment API key, integration ID, and connection ID:
curl "https://api.tenklo.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 Tenklo to inspect requests.
Follow our Auth implementation guide to integrate Tenklo in your app.
To obtain your own production credentials, follow the setup guide linked below.
📚 Pushpay ChMS (v1) guides
- How do I link my Pushpay ChMS account?
Subdomain, API user, and permissions in Pushpay ChMS
Official implementer guide: Pushpay ChMS API documentation
Support article: How to create and manage API users in ChMS
API notes
- Responses are XML; Tenklo forwards the raw body from the proxy.
- Optional
describe_api=1on any service returns accepted parameters without counting against your daily quota. - Rate limits: monitor
X-RateLimit-*headers; on HTTP429, honorRetry-After. There is also a separate daily limit per API user;api_statusreports usage and does not increment the counter.
🧩 Pre-built syncs and actions
Explore Nango-provided actions in your dashboard. Extend and customize them to fit your needs.
No pre-built syncs or actions available yet.