πŸš€
JetPero
  • Welcome to JetPero API Platform
  • Getting Started
    • Quickstart
  • Signup & Setup
  • Your First API Key
  • Basics
    • Integrations
    • API Requests & Responses
    • SDKs & Tools
  • Features
    • API Key Management
    • Monitoring & Analytics
    • Alerts & Notifications
    • Security
  • Plans & Limits
    • Pricing
    • Rate Limits
  • Help
    • Troubleshooting & FAQ
    • Contact Support
Powered by GitBook
On this page
  • πŸ“Š What Are Rate Limits?
  • πŸ“ˆ Default Rate Limits by Plan
  • ⏱ Time Window
  • βš™οΈ Behavior on Exceeding Limits
  • πŸ“˜ Best Practices
  • πŸ›‘οΈ Protection Against Abuse
  • πŸ’‘ Need More Capacity?
  • 🀝 Want Custom Rate Rules?
  1. Plans & Limits

Rate Limits

At JetPero, we apply rate limits to ensure fair usage, maintain high availability, and prevent abuse across our platform. Each pricing plan comes with different thresholds tailored for your API growth

πŸ“Š What Are Rate Limits?

Rate limits define the maximum number of API calls your project can make in a given time window (usually per minute or per month). This protects both your application and our platform from overload.


πŸ“ˆ Default Rate Limits by Plan

Plan
Monthly Call Limit
Per-Minute Limit
Burst Handling

STARTER

5,000 calls/month

10 req/min

None

PRO

40,000 calls/month

50 req/min

Basic queue

BUSINESS

Unlimited*

150 req/min

Smart burst buffer

ENTERPRISE

Custom (5M – 25M+)

500+ req/min

Custom Config

*Business plan has soft limits to ensure fair usage across users. Abuse may lead to throttling or an upgrade prompt.


⏱ Time Window

We use rolling windows to calculate rate usage. For example, if your plan supports 50 requests per minute, the system evaluates usage over the last 60 seconds from any point in time.


βš™οΈ Behavior on Exceeding Limits

If your app exceeds the allowed threshold:

  • 🚫 The request is rejected with HTTP 429 Too Many Requests

  • πŸ•’ Retry-After header tells you when to retry

  • πŸ“¬ Optional: You can configure email or Slack alerts when you're nearing 90% usage (Enterprise only)


πŸ“˜ Best Practices

  • πŸ“Œ Use caching when possible to avoid unnecessary calls

  • 🧠 Batch requests if your API supports it

  • ⏳ Implement exponential backoff when receiving 429 errors

  • πŸ” If you're polling data, switch to webhooks or streaming where applicable


πŸ›‘οΈ Protection Against Abuse

JetPero also implements abuse detection algorithms behind the scenes, such as:

  • Rapid repeated failures from the same IP

  • Suspicious spikes in burst traffic

  • Misuse of API keys

In such cases, traffic may be temporarily blocked even if below quota.


πŸ’‘ Need More Capacity?

Upgrade your plan at any time via the Dashboard to access higher thresholds or contact our team for enterprise scaling needs.


🀝 Want Custom Rate Rules?

JetPero’s Enterprise Tier supports:

  • Endpoint-specific throttling

  • User-based or team-based quotas

  • Regional IP limit configs

  • Multi-environment isolation

πŸ“ž Contact Sales to discuss your custom setup.

PreviousPricingNextTroubleshooting & FAQ

Last updated 1 month ago