Holistics · Rate Limits

Holistics Rate Limits

Holistics does not publish specific numeric REST API rate limits in its public documentation. Programmatic access is authorized per user via the X-Holistics-Key header, and query and export work is executed asynchronously as jobs that are polled for status, which naturally bounds concurrency. Practical limits are governed by report/dataset query complexity, the underlying data warehouse, and account/plan scope. Specific per-account values are not reconciled in this artifact.

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

It captures 4 rate-limit definitions, measuring requests and jobs.

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

Tagged areas include Business Intelligence, Analytics, Self-Service BI, Data Modeling, and Embedded Analytics.

4 Limits Throttle: 429
Business IntelligenceAnalyticsSelf-Service BIData ModelingEmbedded AnalyticsRate LimitingQuotasThrottling

Limits

Per-User API Key user
requests
see provider documentation
Access is authorized by a per-user API key; no public numeric request cap is documented.
Query Job Concurrency account
jobs
see provider documentation
Report and dataset queries run as asynchronous jobs polled for results; concurrency is bounded by account and warehouse.
Export Job Concurrency account
jobs
see provider documentation
Export jobs (CSV/JSON/XLSX) run asynchronously and are downloaded once status is success.
Data Pipeline Execution account
jobs
see provider documentation
Data import and transform executions are queued as ETL jobs; throughput depends on the data pipeline and warehouse.

Policies

Asynchronous Jobs
Queries, exports, and pipeline runs execute as jobs; clients poll job status endpoints rather than holding long synchronous connections.
Backoff Strategy
Clients should poll job status with reasonable intervals and implement exponential backoff with jitter on 429/5xx responses.

Sources