Tigergraph Rate Limits
The TigerGraph REST++ API does not publish fixed per-second request quotas; throughput is governed by the database server's configuration and the size of the deployed workspace. REST++ exposes RESTPP.Factor.DefaultQueryTimeout (the GSQL.QUERY timeout) and a configurable maximum response buffer/result size, and concurrent query execution is bounded by the workspace's CPU and memory. On TigerGraph Savanna, effective throughput scales with the chosen workspace size, and customer level (Free, Paid, Premium, Enterprise) governs workspace count and resource quotas. Specific numeric limits are not reconciled here.
Tigergraph Rate Limits is the machine-readable rate-limit profile for TigerGraph on the APIs.io network, in the API Commons Rate Limits shape.
It captures 4 rate-limit definitions, measuring seconds, bytes, queries, and workspaces.
An exhausted limit returns HTTP 503.
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 Graph Database, Analytics, GSQL, REST++, and Graph Analytics.
generated, dated 2026-06-20.
Limits
Policies
Sources
- https://docs.tigergraph.com/tigergraph-server/current/api/built-in-endpoints
- https://docs.tigergraph.com/savanna/main/resources/quota_policy
- https://docs.tigergraph.com/tigergraph-server/current/reference/configuration-parameters
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.