MarketCheck implements rate limiting and quota management through custom HTTP headers that provide detailed information about your API usage, remaining capacity, and reset times.
MarketCheck adds comprehensive headers to all API responses to help you monitor your usage and plan your API calls effectively.
| Header | Description |
|---|---|
RateLimit-Limit | Maximum number of requests allowed per second |
RateLimit-Remaining | Number of requests remaining in the current second |
RateLimit-Reset-Time | ISO timestamp indicating when the rate limit resets |
| Header | Description |
|---|---|
Quota-Limit | Maximum number of requests allowed per month |
Quota-Remaining | Number of requests remaining in the current month |
Quota-Reset-Time | ISO timestamp indicating when the monthly quota resets |
| Header | Description |
|---|---|
Retry-After | Number of seconds to wait before making another request. For example, if you exceed your monthly quota, this shows seconds until the next month (e.g., 86500 = ~24 hours remaining in current month) |
When rate limits or quotas are exceeded, MarketCheck returns structured error responses with detailed information to help you understand the issue and determine the appropriate retry strategy.
Example Response — Monthly Quota Exceeded:
HTTP/1.1 429 Too Many Requests
Content-Type: application/json
RateLimit-Limit: 5
RateLimit-Remaining: 0
RateLimit-Reset-Time: 2025-07-22T14:30:16Z
Quota-Limit: 100000
Quota-Remaining: 0
Quota-Reset-Time: 2025-08-01T00:00:00Z
Retry-After: 86500
{
"message": "Monthly API quota exhausted"
}
MarketCheck provides specific error messages based on the type of limit that was exceeded:
Rate Limit Exceeded:
{
"message": "API rate limit exceeded"
}
Monthly Quota Exhausted:
{
"message": "Monthly API quota exhausted"
}
RateLimit-Remaining and Quota-Remaining headers to track your usageRetry-After header value when receiving 429 responses