Stay organized with collections
Save and categorize content based on your preferences.
Chronicle API quotas
Chronicle API quotas are enforced at the server level using an interceptor.
Each service that integrates with Chronicle API needs to specify the appropriate
quota server key to enable quota enforcement.
The following table lists the quotas that are being enforced, where:
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-04 UTC."],[[["Chronicle API enforces quotas at the server level using an interceptor, requiring each integrating service to specify the correct quota server key."],["The API query quotas are categorized by Queries Per Second (QPS), Queries Per Minute (QPM), and Queries Per Day (QPD)."],["Search APIs like `ListAlerts`, `ListEvents`, `ListIocs`, and `ListIocDetails` have a quota of 1 QPS, while `ListAssets` has a quota of 5 QPS, and `SearchRawLogs` has a quota of 1 QPM."],["The `Partner` group's `CreateCustomer` API has a quota of 10 QPD."],["The `Rules` group includes a wide array of APIs for managing detections, retrohunts, and rules, with most having a 1 QPS quota, except for `ListDetections` which is 10 QPM, and `StreamTestRule`, which is 3 QPM."]]],[]]
