All requests to Searchspring servers are rate limited. This ensures that our system is reliable and secure for all our clients.
What is rate limiting?
All systems have limited thresholds. When overloaded with too many requests, servers experience outages which affect every end user. Rate limits are used by web services to restrict the number of requests that clients can make within a time frame.
We strive to provide a fair and reliable service for each of our customers. To prevent abuse and protect our servers from overuse, we limit the number of requests that a customer can send to our server. This protects our system against attacks, excessive usage scraping and bots.
How can I avoid hitting my rate limit?
Our servers use best practices to ensure that you do not hit your rate limit. Here are some of the safeguards that we have in place:
- Caching: We use edge-caching to reduce the number of requests that are made to our server
- Monitoring: Ongoing monitoring allows us to identify and action errors to reduce retry requests
- Optimization: We only request required data to avoid low value requests
What happens if I hit my rate limit?
Depending on how many requests were sent to the system, you may need to wait anywhere from a few seconds to a few minutes before more requests can be made.