Usage Quotas

The Kard API leverages usage quotas to manage API throughput. Upon integration, the correct usage quotas will be determined based on your access patterns and client tier, and these can be configured if a higher usage quota is needed. Kard’s usage quotas are built to make sure we can provide the optimal experience for your users.

Usage quotas refill continuously and are evaluated on a per minute basis. If your usage quota is exceeded, the response will return a 429 - Too Many Requests error.

Each request to Kard’s API will have the following response headers:

  • Kard-Api-Usage-Quota-Capacity: this header represents the overall capacity available to you on a per minute basis.
  • Kard-Api-Usage-Quota-Remaining: the number of remaining requests you can perform within the next minute.
  • Kard-Api-Usage-Quota-Reset: when Kard-Api-Usage-Quota-Remaining is 0, this number will indicate how long, in seconds, before you can make another successful request. If Kard-Api-Usage-Quota-Remaining > 0, this value will be 0.

A response header example:

Content-Type: application/json
Content-Length: 20
Date: Tue, 06 Dec 2024 12:00:00 GMT
X-Cache: HIT
...
Kard-Api-Usage-Quota-Capacity: 1000
Kard-Api-Usage-Quota-Remaining: 750
Kard-Api-Usage-Quota-Reset: 0

In this case, the client:

  • Has a capacity of 1000 API requests per minute
  • Can perform 750 more API requests within the next minute
  • Has a reset value of 0, as subsequent API requests can be made within the minute. If the quota remaining is 0, the reset will have a value between 1-60 outlining the seconds before another successful request can be made.
Built with