Understanding Rate Limits
Rate limits define the maximum number of requests your application can make during a given period of time. If a limit is exceeded, the API will temporarily reject additional requests until your quota resets. To build reliable integrations, we recommend:- Batching requests where appropriate
- Using webhooks instead of polling when possible
- Caching responses that do not require real-time updates
- Implementing retries with exponential backoff
Demo API Key Rate Limits
When you create an API Key in the Developer Portal, it is assigned to the Demo Plan (Free). The following are the rate limits allocated to a Demo Tier API Key:- 2,000 Compute Units (CUs) per month
- 2 requests per second
- Burst capacity: 5 requests
Need higher limits? Production and enterprise tiers offer significantly increased rate limits. Contact us at info@webacy.com to upgrade your plan.
Handling Rate Limits
When you exceed the rate limit, the API returns a429 Too Many Requests response:
Best Practices
- Cache responses - Avoid redundant API calls for the same data
- Batch requests - Use batch endpoints where available
- Monitor usage - Use the API Usage endpoint to track consumption
- Implement queuing - Queue requests during high-traffic periods
Scaling your Integration
When your integration is production-ready and you need higher limits:- Developer Portal - Upgrade at developers.webacy.co
- Account Manager - Contact your account manager for enterprise plans
- Support - Email info@webacy.com
Whatβs Next
Compute Units (CUs)
Learn how Compute Units measure the processing and intelligence required for each Webacy API request.
