Rate Limits
The ListHouze API enforces rate limits to ensure fair usage and platform stability for all customers. Understanding these limits helps you design integrations that run reliably without hitting throttling errors. This guide covers the default quotas, how limits are communicated in response headers, and strategies for staying within bounds.
Default Rate Limits
API requests are limited based on your subscription plan. Free plans allow 60 requests per minute, Professional plans allow 300 requests per minute, and Enterprise plans allow 1,000 requests per minute. Bulk endpoints count as a single request regardless of the number of records included. Rate limits reset on a rolling one-minute window.
Reading Rate Limit Headers
Every API response includes rate limit headers: X-RateLimit-Limit shows your total allowance, X-RateLimit-Remaining shows how many requests you have left in the current window, and X-RateLimit-Reset provides the Unix timestamp when the window resets. Monitor these headers to proactively throttle your application before hitting the limit.
Best Practices for Staying Within Limits
Use caching to avoid redundant requests, batch operations with bulk endpoints where possible, and implement exponential backoff when you receive a 429 Too Many Requests response. For high-volume use cases, consider using webhooks instead of polling to reduce your request count significantly.
Info