# API rate limit

GLOSSARY, read 10 Nov 2026

**Definition.** An API rate limit caps how many requests a client may send in a period, and the server answers excess requests with an error. Brinqa's BQL API sets separate limits for starting queries and fetching results, and replies 429 Too Many Requests with a Retry-After header when a limit is exceeded.

Export and load jobs hit rate limits first. Build the migration scripts to read the Retry-After value and back off, rather than retrying at a fixed interval.

Kenna's reference pages read on 2026-11-10 give batch sizes, such as 30,000 assets per bulk update and 2,000 findings per bulk delete, but no request-rate figure was found there on 2026-11-10. Ask the vendor before sizing a load window.

## A sourced example

Brinqa's BQL API documentation describes 429 responses with a Retry-After header and recommends exponential backoff when the rate limit is exceeded.

## Related terms

- [pagination](/glossary/pagination/)
- [data export](/glossary/data-export/)
- [bulk export](/glossary/bulk-export/)
- [JSON Lines](/glossary/json-lines/)

## Sources

- Source for the example: API rate limit: https://docs.brinqa.com/docs/brinqa-api (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/glossary/api-rate-limit/
