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, in the API Commons Rate Limits shape.

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

An exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

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 Exhausted: HTTP 429
Method: generated, dated 2026-07-10.
Written by API Evangelist on 2026-07-10 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
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

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/quenza-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.