Skip to main content

API rate limits

The following rate limits for public GravityZone API.


If a method is not included in the following table, the default rate limit applies, which is 10 request per minute per API.

Rate limit parameters

Requests per burst*




10 requests per second per API Key

10 requests

No delay

This rate limit applies to any API method that is not listed below.

5 requests per second per API Key

5 requests

No delay

Licensing API

  • getLicenseInfo

  • setLicenseKey

  • addProductKey

  • removeProductKey

  • getMonthlyUsage

  • getMonthlyUsagePerProductType

Companies API

  • deleteCompany

  • updateCompanyDetails

  • suspendCompany

  • activateCompany

  • createCustomFieldDefinition

  • updateCustomFieldDefinition

  • getCustomFieldsDefinitions

  • deleteCustomFieldDefinition

30 requests per minute per API Key

10 requests

No delay

Quarantine API

  • createRemoveQuarantineItemTask

  • createEmptyQuarantineTask

  • createRestoreQuarantineItemTask

  • createRestoreQuarantineExchangeItemTask

  • createAddFileToQuarantineTask

  • createReleaseQuarantineExchangeItemTask

Network API

  • createScanTask

  • createReconfigureClientTask

  • createScanTaskByMac

  • moveCompanyOrCompanyFolder

  • moveEndpointsBetweenCompanies

  • deleteEndpoint

Integrations API

  • configureAmazonEC2IntegrationUsingCrossAccountRole

Licensing API

  • setMonthlySubscription

Accounts API

  • createAccount

  • deleteAccount

  • updateAccount

  • configureNotificationsSettings

  • getNotificationsSettings

5 requests per minute per API Key

Not available

No delay

Incidents API

  • addToBlocklist

  • removeFromBlocklist

  • createCustomRule

  • deleteCustomRule

Network API

  • assignPolicy

Event Push Service API

  • setPushEventSettings

  • getPushEventSettings

  • sendTestPushEvent

  • getPushEventStats

  • resetPushEventStats

Maintenance windows API

  • updatePatchManagementMaintenanceWindow

  • deleteMaintenanceWindow

  • assignMaintenanceWindows

  • unassignMaintenanceWindows

*the burst mechanism is based on a queue that stores a specific number of API requests that would normally exceed the rate limit applicable. Requests will be stored and ran in the order they were requested. If the burst queue is full, any additional requests will return a 429 HTTP error code.


If the burst mechanism is not available for a specific API method, the requests will not be queued. Any request that exceeds the rate limit will return a 429 HTTP error code.

**an API request delay mechanism activates when the method rate limit is reached and will delay the processing of the request until the time limit has passed. If No delay is applicable to a method, the public API service will consume the queue as soon as it arrives.