Tithe.ly · Rate Limits

Tithely Rate Limits

Tithe.ly does not publish fixed numeric rate limits in its public documentation. The API is access-gated - approved partners receive public and private API keys and are expected to build against a test environment (tithelydev.com) before promoting to live (tithe.ly). Any specific per-key throttles, concurrency ceilings, or payment velocity controls would be communicated to approved integrators through the private developer materials rather than the public docs. Clients should implement retry-with-backoff and treat payment operations as non-idempotent unless an idempotency mechanism is provided.

Tithely Rate Limits is the machine-readable rate-limit profile for Tithe.ly on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 3 rate-limit definitions, measuring requests and transactions.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Church Giving, Payments, API, Rate Limiting, and Quotas.

3 Limits Throttle: 429
Church GivingPaymentsAPIRate LimitingQuotas

Limits

API Requests api-key
requests
not published
No fixed numeric request-rate limit is documented for the V1 or V2 API.
Payment / Charge Velocity organization
transactions
not published
Payment and charge operations may be subject to risk/velocity controls that are not publicly documented.
Test Environment api-key
requests
sandbox
Integration testing is done against tithelydev.com with test keys before going live.

Policies

Access by Request
API access is granted by request to organizations using or moving to Tithe.ly; keys are issued on approval.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.
Test Before Live
Build and validate against the tithelydev.com test hosts before switching to the live tithe.ly hosts.

Sources