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:

Endpoint-Specific Limits

Different endpoints have different rate limits based on their resource intensity:

Rate Limit Error Response

When you exceed the rate limit, you’ll receive a 429 response:

Example Response Headers

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

Response

429