Qgiv · Rate Limits

Qgiv Rate Limits

Qgiv does not publish numeric rate limits anywhere in its API documentation (qgiv.com/api). Access is scoped by API token to specific form(s) rather than by a stated requests-per-minute or requests-per-day ceiling, and no documented endpoint returns a standard 429 status or rate-limit headers (X-RateLimit-*, Retry-After, etc.). This is consistent with the API's age and design as a small, form-scoped reporting/configuration surface rather than a high-volume public platform API.

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

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

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

Tagged areas include Nonprofit, Fundraising, Donations, Payments, and Rate Limiting.

3 Limits Throttle: not documented
NonprofitFundraisingDonationsPaymentsRate LimitingQuotas

Limits

API Requests token
requests
not published
No fixed numeric request-rate limit is documented for any endpoint.
Form Scope token
forms
per-token, admin-configured
Access is bounded by which form(s) an API token is associated with in the Qgiv admin console, not by a request-rate quota.
Transaction Polling Cadence integration
requests
not published
No documented push/webhook mechanism exists for transactions; integrators must poll last/after/dates endpoints, but no recommended or enforced polling interval is published.

Policies

No Documented 429 Behavior
No throttling response code or Retry-After header is documented anywhere in the Qgiv API reference as of the review date.
Recommended Client Behavior
In the absence of published limits, API Evangelist recommends conservative polling intervals and exponential backoff on errors as a defensive default.

Sources