Qlik Sense · Rate Limits

Qliksense Rate Limits

Published Qlik Cloud API rate limits. REPLACES a fabricated scaffold written by the 2026-05-04 bulk sweep, which invented free/professional/enterprise tiers at 10/100/1000 rpm and X-RateLimit-* headers Qlik does not emit. Qlik's real model is per tier, per user, per tenant — and every plan gets the SAME limits; they are not negotiable per customer.

Qliksense Rate Limits is the machine-readable rate-limit profile for Qlik Sense on the APIs.io network, in the API Commons Rate Limits shape.

It captures 3 rate-limit definitions, across the Tier 1, Tier 2, and Special tiers, measuring requests_per_minute.

Limit state is signalled in the retryAfter, limit, remaining, and reset response headers, and an exhausted limit returns HTTP 429.

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

Tagged areas include Analytics, Business Intelligence, Cloud, Rate Limiting, and Quotas.

3 Limits Exhausted: HTTP 429 Quota: 429 retryAfterlimitremainingreset
Transcribed from the provider's documentation on 2026-08-29 — qlik.dev/apis/rest/rate-limiting/ for the tier model, the....
View Source
AnalyticsBusiness IntelligenceCloudRate LimitingQuotasThrottling

Limits

per-tier per-user per-tenant
requests_per_minute · minute
1000/5-minute rolling
per-tier per-user per-tenant
requests_per_minute · minute
100/5-minute rolling
per-operation
requests_per_minute · minute
See special_endpoints[] below — limits observed range from 10 to 1,000 rpm.

Policies

Retry-After
Clients must wait the number of seconds in the Retry-After header before retrying. Qlik publishes worked retry examples for @qlik/api, Node.js and other clients.
Toolkit handling
Rate-limit handling is built into qlik-cli and into the Qlik Cloud Services / Qlik Platform Operations connectors in Qlik Automate.
Error-response limits
Qlik states that some endpoints carry ADDITIONAL rate limits on error responses.
Subject to change
Qlik states each tier's limits are subject to change.
Unpublished endpoints
Endpoints not documented on qlik.dev are private but may share a tier with published ones — so private traffic can consume a published endpoint's budget.

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/qliksense-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.