Community
Questions Library
Docs
Blog
Events
Swag
Github
Slack
JupiterOne
Discussions
Release Notes
Contact Us
J1QL Query Rate Limiting - AskJ1 Community
<main> <article class="userContent"> <p>J1QL queries executed via the <a rel="nofollow" href="https://jupiterone.vanillacommunities.com/kb/articles/794-jupiterone-api">J1 public API</a> are rate-limited separately from <a rel="nofollow" href="https://jupiterone.vanillacommunities.com/kb/articles/1302-jupiterone-graphql-api-rate-limiting">GraphQL API invocations</a>. Each J1QL query consumes one request token. All queries executed via the J1 public API count towards the rate limit. This count includes user-initiated application queries (such as search and J1 Insights) and queries via the J1 public API. You should incorporate retry with backoff in response to rate-limiting responses from the J1 API.</p> <h4 data-id="account-rate-limit-for-j1ql-queries"><strong>Account Rate Limit for J1QL Queries</strong></h4> <ul><li>Default limit: 120 tokens/120 seconds</li> <li>Enterprise limit (available on request): 60 tokens/60 seconds</li> <li>Enterprise customers are eligible for a rate limit increase up to 120 tokens/60 seconds, subject to usage analysis and approval. Contact your J1 TSE to request an increase.</li> </ul> </article> </main>