Skip to main content
The lobstr.io API enforces rate limits to ensure fair usage and stable service performance. When you exceed the rate limit, the API returns a 429 Too Many Requests response.

​
Rate Limit Headers

Every API response includes headers to help you track your rate limit usage:
HeaderDescription
X-RateLimit-LimitTotal requests allowed per minute
X-RateLimit-RemainingNumber of requests remaining in the current rate limit window
X-RateLimit-ResetUNIX timestamp indicating when the rate limit window resets
Retry-AfterSeconds until you can retry after hitting the limit

​
Endpoint-Specific Limits

Different endpoints have different rate limits based on their resource intensity:
EndpointLimit
/v1/squids120 requests/minute
/v1/tasks90 requests/minute
/v1/runtasks90 requests/minute
/v1/runs120 requests/minute
/v1/results2 requests/second

​
Rate Limit Error Response

When you exceed the rate limit, you’ll receive a 429 response: 
{
  "error": "Rate limit exceeded. Please try again later.",
  "type": "RateLimitExceeded",
  "code": 429
}

​
Example Response Headers

X-RateLimit-Limit: 120
X-RateLimit-Remaining: 0
X-RateLimit-Reset: 1716909300
Retry-After: 45
Monitor the X-RateLimit-Remaining header to proactively slow down requests before hitting the limit.
The /v1/results endpoint has a stricter limit (2 req/sec) due to the data-intensive nature of result retrieval.
Repeatedly hitting rate limits may result in temporary IP blocks. Implement exponential backoff in your code.
Use the Retry-After header value to know exactly when to retry your request.

​
Code Examples

curl -i -X GET "https://api.lobstr.io/v1/results" \
  -H "Authorization: Token YOUR_API_KEY"

​
Response

429
{
  "error": "Rate limit exceeded. Please try again later.",
  "type": "RateLimitExceeded",
  "code": 429
}