Quenza · Rate Limits

Quenza Rate Limits

Quenza does not publish fixed numeric request-rate limits for the v1 REST API in its public reference. The documented throughput control is pagination - list endpoints accept offset and limit query parameters, with a maximum limit of 100 items per request and a default of 20. Practical usage is also bounded by the subscription tier that unlocks API access (Collective and Beyond) and by that tier's client, professional, and webhook allowances rather than by a documented per-minute request cap.

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

It captures 4 rate-limit definitions, measuring requests, items, plan, and webhooks.

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

Tagged areas include Coaching, Therapy, Client Engagement, Rate Limiting, and Quotas.

4 Limits Throttle: 429
CoachingTherapyClient EngagementRate LimitingQuotas

Limits

API Request Rate account
requests
not published
No fixed numeric request-rate limit is documented for the Quenza v1 REST API.
Pagination Page Size request
items
100
List endpoints accept limit (default 20, max 100) and offset query parameters.
API Access Eligibility account
plan
Collective and Beyond only
The v1 API is a plan-gated feature; Spark, Growth, and Impact do not include API access.
Webhooks account
webhooks
per plan (Growth 1, Impact 2, Collective 5, Beyond unlimited)
Outbound webhook count is capped by subscription tier.

Policies

Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on any 429 responses, since numeric limits are not published.
Pagination
Iterate large collections using offset and limit (max 100) and follow the links.next / links.prev cursors returned in list responses.

Sources