To ensure high levels of service for all users of the PrimaryBid Connect API we apply usage limits to our APIs.
Unless otherwise stated, limits are applied at the IP address level. We may occasionally adjust limits to prevent system abuse, and in this case, we will notify you in advance.
Concurrent rate limits restrict the maximum number of simultaneous requests-per-second (RPS) you can make to our APIs. The purpose is fourfold:
- To combat overuse that could render the API unavailable for all end users.
- To help protect against slow performance and malicious bot attacks such as brute-force (BF) attacks, denial-of-service (DoS/DDoS) attacks, and web scraping.
- To provide our Partners with seamless reliability and scalability.
- To deliver the best possible API experience, by ensuring the safety of both the API and its users.
We have enforced a limit of 150 RPS across all endpoints.
When this limit is exceeded, API requests will be rejected with an HTTP 429 code (Too many requests). Should you require a higher rate limit of API usage, please reach out to a Solutions Engineer.