API Rate Limits

Learn about Hyperping's API rate limiting system and how to work within the limits.

To ensure fair usage and maintain service reliability, Hyperping implements rate limiting on all API endpoints. These limits are designed to allow normal usage patterns while preventing abuse.

Default Rate Limits

By default, all projects are limited to 800 requests per hour per project. This limit is calculated on a rolling window basis.

How Rate Limiting Works

Rate limits are enforced using the following mechanism:

• Time window: 1 hour rolling window
• Identification: Requests are tracked per project using your API token
• Fallback: If no valid token is provided, limits are applied per IP address
• Response: When exceeded, the API returns a 429 Too Many Requests status

Authentication

To make API requests, you'll need to use your API token which you can find at app.hyperping.io/project/developers. Include this token in your requests using the Authorization header:

Authorization: Bearer your-api-token-here

Rate Limit Headers

API responses include rate limit information in the ratelimit header to help you track your usage:

ratelimit: "2000-in-1hr"; r=1992; t=3481

The header format includes:

• "2000-in-1hr" - Your rate limit (2000 requests per hour in this example)
• r=1992 - Remaining requests in the current window
• t=3481 - Time until reset (in seconds)

When the rate limit is exceeded, you'll also receive a retry-after header indicating how many seconds to wait before making another request.

Increased Limits for Paid Plans

If you're on a paid plan and need higher rate limits for your use case, we can increase them for your project. Simply contact our support team with your requirements.

Common scenarios for increased limits include:

• High-frequency monitoring applications
• Bulk data synchronization
• Integration with third-party systems
• Automated reporting tools

Best Practices

To make the most efficient use of your API quota:

• Implement exponential backoff - When you receive a 429 response, wait before retrying
• Cache responses - Avoid unnecessary repeated calls for the same data
• Batch operations - Use bulk endpoints when available
• Monitor your usage - Keep track of rate limit headers in your responses
• Use webhooks - For real-time updates, consider webhooks instead of polling

Error Response Example

When you exceed the rate limit, you'll receive a response like this:

HTTP/1.1 429 Too Many Requests
ratelimit: "800-in-1hr"; r=0; t=3590
retry-after: 3590

Rate limit exceeded

Requesting Higher Limits

To request increased rate limits for your paid plan:

1. Contact our support team via chat or email at hello@hyperping.io
2. Let us know which project needs increased limits and your current usage patterns
3. Explain your use case and required limits
4. We'll review and apply the increased limits to your project

Need Help?

If you have questions about rate limits or need assistance optimizing your API usage, don't hesitate to reach out via chat or email at hello@hyperping.io.