Skip to content
Last updated

To ensure the stability, availability, and fair usage of our services, Creditsafe applies rate limiting to incoming API requests. This means that there is a maximum number of requests that can be accepted from an individual client within a one minute time window.

Rate limiting is used to protect our operational environments and to prevent excessive traffic from one client negatively affecting other customers. These safeguards help ensure consistent service quality for all users.


HTTP 429 — Too Many Requests

Client implementations must be designed to handle situations where request limits are temporarily reached. In such cases, the service will respond with HTTP status code 429 (Too Many Requests). When this occurs, clients are expected to pause further requests and resume only after a suitable waiting period.


Implementation Requirements

Implementations should include logic to:

  • Detect rate-limit responses (HTTP 429)
  • Temporarily suspend request execution
  • Continue processing once additional requests can be accepted
Resuming Too Early

Resuming request execution too early may result in continued throttling and effectively prolong the period during which requests are blocked.