Tithe.ly is a church-technology platform for online and mobile giving, church management (ChMS), branded church apps, websites, events, and messaging. Its developer API lets churches and approved partners create donations, tokenize cards and bank accounts for PCI-safe payments, charge one-time and recurring gifts, manage giving funds (payment categories), and look up organizations.
Access is gated. The Tithe.ly API is granted by request to organizations that use (or are moving to) Tithe.ly. You email [email protected], describe what you want to build, and approved requesters receive public and private API keys by email. Integrators build and validate against a test environment (tithelydev.com) before promoting to the live environment (tithe.ly). Two generations are documented: a V1 payments/tokenization API (Tithely.js plus charge endpoints) and a V2 REST API (organizations, transactions, funds, and mail).
Because full field-level request/response schemas live behind the approved-partner developer docs, the OpenAPI in this entry documents the publicly listed paths and methods with modeled request and response bodies. See review.yml for the confirmed vs. modeled breakdown.
APIs.json: https://raw.githubusercontent.com/api-evangelist/tithely/refs/heads/main/apis.yml
- Church Giving
- Donations
- Fundraising
- Payments
- Nonprofit
- ChMS
- Faith
- Created: 2026-07-03
- Modified: 2026-07-03
- V2 REST API (
https://tithe.ly/api/v2): headerAuthorization: {API_ID}:{API_TOKEN}. ThePOST /loginendpoint is the only V2 call that does not require the header. - V1 payments API (
https://tithe.ly/api/v1, testhttps://tithelydev.com/api/v1): uses the private key issued on approval; payment methods are created from tokens produced client-side by Tithely.js.
Create donation transactions (one-time or recurring) against an organization and a payment category (fund) using a tokenized payment method.
- Human URL: https://tithe.ly/api/v2/docs
- Base URL:
https://tithe.ly/api/v2
PCI-safe payment flow. Tithely.js renders a hosted iframe to tokenize a card or bank account client-side; the resulting token is attached to a user via payment-methods and charged with charge (repeat/recurring) or charge-once (one-time).
- Human URL: https://docs.tithe.ly/reference/tokenization-with-tithelyjs-v2
- Base URL:
https://tithe.ly/api/v1(testhttps://tithelydev.com/api/v1)
Retrieve one or more Tithe.ly organizations (churches) by ID, and search organizations by owner.
- Human URL: https://tithe.ly/api/v2/docs
- Base URL:
https://tithe.ly/api/v2
Create, read, and update payment categories - Tithe.ly's giving funds that donations are allocated to for a given organization.
- Human URL: https://tithe.ly/api/v2/docs
- Base URL:
https://tithe.ly/api/v2
Send templated transactional emails (such as giving receipts and notifications) to recipients on behalf of an organization.
- Human URL: https://tithe.ly/api/v2/docs
- Base URL:
https://tithe.ly/api/v2
Authenticate a user and obtain the credentials used for subsequent V2 calls.
- Human URL: https://tithe.ly/api/v2/docs
- Base URL:
https://tithe.ly/api/v2
POST /api/v2/loginGET /api/v2/organization/{id}GET /api/v2/organization-owner/{id}GET /api/v2/payment_category/{id}POST /api/v2/payment_categoryPUT /api/v2/payment_category/{id}POST /api/v2/transactionPOST /api/v2/mailPOST /api/v1/payment-methodsPOST /api/v1/chargePOST /api/v1/charge-once
Online giving has a free-forever plan (no monthly fee); churches pay per-transaction processing fees: ~2.9% + $0.30 (card), ~1% + $0.30 (ACH), ~3.5% + $0.30 (Amex). Donors can opt to cover fees. Software subscriptions (ChMS ~$72/mo, All-Access ~$119/mo) and Enterprise (custom) add fixed cost. The API itself has no separate metered price. Verify current rates at get.tithe.ly/pricing. See plans/tithely-plans-pricing.yml, rate-limits/tithely-rate-limits.yml, and finops/tithely-finops.yml.
Does Tithe.ly expose a documented public WebSocket API? No. Tithe.ly's documented developer surface is request/response REST (V1 payments + V2 REST) plus the browser-side Tithely.js tokenization library. No WebSocket or public webhook/event-subscription surface is documented. See review.yml.
FN: Kin Lane Email: [email protected]