Skip to main content
SOC Defenders enforces rate limits to ensure consistent performance for all users. Limits apply per API key and reset on a rolling basis. If you exceed a limit, the API returns a 429 Too Many Requests response until the window resets.

​
Limits by tier

If your use case requires higher throughput, a longer lookback period, or more results per request, upgrade to the Pro tier. See Pricing for details.

​
Rate limit response headers

Every API response includes headers that tell you your current usage against the active limit: Monitor these headers in your integration to stay within your quota and back off proactively before hitting a limit.

​
429 Too Many Requests

When you exceed a rate limit, the API responds with:
Wait until the timestamp in X-RateLimit-Reset before retrying. Use exponential backoff for automated retry logic.

​
Best practices

Use the since parameter for delta polling. Rather than re-fetching the full IOC or article feed on each run, pass a since timestamp to retrieve only records that have changed since your last successful request. This significantly reduces your daily request count.
Cache results locally. If multiple services or team members query the same data, fetch it once and distribute from a local cache rather than issuing redundant API calls. Page efficiently. Use the maximum limit your tier allows per request to retrieve more data in fewer calls.