Rate limiting is managed through a weighted scoring system, known as Compute Units (CUs). Each API request consumes a specified number of CUs, determined by the complexity of the request. This system is designed to accommodate basic requests while efficiently handling more computationally intensive operations.

​
Rate Limit Tiers

The maximum CUs (rate-limiting score) for a user depends on their subscription level and is delineated in the following table:

Subscription LevelPer Minute Limit (CUs)Per Day Limit (CUs)
Unauthenticated6,0001,200,000
Free8,0002,000,000
Base10,0003,750,000
Growth14,00011,200,000
Pro20,00025,000,000

To update your subscription level use the AvaCloud Portal

Note: Rate limits apply collectively across both Webhooks and Data APIs, with usage from each counting toward your total CU limit.

​
Rate Limit Categories

The CUs for each category are defined in the following table:

WeightCU Value
Free1
Small10
Medium20
Large50
XL100
XXL200

​
Rate Limits for Webhook Endpoints

The CUs for each route are defined in the table below:

EndpointMethodWeightCU Value
/v1/webhooksPOSTMedium20
/v1/webhooksGETSmall10
/v1/webhooks/{id}GETSmall10
/v1/webhooks/{id}DELETEMedium20
/v1/webhooks/{id}PATCHMedium20
/v1/webhooks:generateOrRotateSharedSecretPOSTMedium20
/v1/webhooks:getSharedSecretGETSmall10
/v1/webhooks/{id}/addressesPATCHMedium20
/v1/webhooks/{id}/addressesDELETEMedium20
/v1/webhooks/{id}/addressesGETMedium20
All rate limits, weights, and CU values are subject to change.

Was this page helpful?

Ethers vs WebhooksMonitoring multiple addresses