Rate Limits

api rate limits klevu's api ecosystem is designed to facilitate efficient communication and robust operations, making it an integral part of our product discovery suite to maintain optimal performance and ensure stability, rate limits are applied to manage the volume of requests overview of rate limits klevu uses a web application firewall (waf) to enforce rate limits this system monitors incoming requests and applies restrictions when the defined thresholds are exceeded these limits are particularly relevant for managing data ingestion into the klevu backend, where processing times may vary based on payload size and complexity key specifications request limit 200 requests per minute scope applies to all indexing related apis, including put, patch, and attribute fetch endpoints payload size each request must adhere to klevu's 2 mb payload size limit to ensure efficient processing and avoid rejection response when limit is exceeded if the request volume surpasses the allowed limit, the api will return http status code 429 (too many requests) message "rate limit exceeded" in such cases where limits are exceeded, additional requests must be paused until the rate resets recommendations for effective api usage to make the most of klevu's api capabilities while staying within the rate limits, consider these best practices batch operations whenever possible, consolidate multiple operations into a single request this reduces the overall number of api calls and optimizes resource usage, ensuring efficient catalog management optimize payload size ensure that each request complies with the 2 mb payload size limit oversized payloads may experience delays or rejection, impacting integration performance account for processing variability the time required to process requests depends on their size and complexity design your integration workflows to handle variable processing times by incorporating delays or retries where necessary