API Rate Limits

Understanding VulnCheck API rate limits for community users

Overview

VulnCheck implements rate limiting to ensure fair usage and maintain optimal performance for all users. Rate limits help protect our infrastructure while providing reliable access to our vulnerability data.

Community User Limits

Community user API requests are limited to 1,000 requests per minute. This limit applies to all API endpoints.

What Happens When Limits Are Exceeded

When you exceed the rate limit, the API will return:

  • HTTP Status Code: 429 "Too Many Requests"
  • Response Format: Standard VulnCheck error JSON structure
{
  "error": true,
  "errors": [
    "Rate limit exceeded. Please try again later."
  ]
}

Best Practices to Avoid Rate Limiting

To ensure smooth API usage and avoid hitting rate limits, consider implementing these strategies:

1. Implement Exponential Backoff

When you receive a 429 response, wait before retrying your request. Start with a short delay and increase it exponentially with each subsequent failure.

2. Cache API Responses

Store API responses locally when appropriate to reduce the number of requests needed. This is especially useful for:

  • Static vulnerability data
  • Index listings that don't change frequently
  • Reference data like CPE information

3. Monitor Your Usage

Keep track of your API usage patterns to identify opportunities for optimization and ensure you stay within limits.

Upgrading for Higher Limits

If you need higher rate limits for your use case, consider upgrading to a paid VulnCheck plan. Paid plans offer:

  • Increased rate limits
  • Access to additional datasets
  • Premium support
  • Enhanced features

Visit vulncheck.com to explore our pricing options and find a plan that meets your needs.