API Rate Limits

​

📊 API Rate Limits & Overage Policy

Aptly enforces API usage limits to ensure reliability and fairness across all tenants. These limits vary by subscription tier and are monitored on a per-tenant basis.

​

🚦 Plan Tiers & API Limits

​

💰 API Overage Pricing

Example: If a tenant on an Enterprise plan makes 300,000 calls in a month:

• Included: 250,000 calls
• Overage: 50,000 × $0.003 = **$150/month** → $1,800/year

​

🚨 Enforcement & Fair Use

• Burst Handling: Short bursts up to 2× the per-minute rate are allowed to support sync operations and multi-threaded workflows.
• Rate Limit Breaches: Requests beyond monthly or per-minute limits return a 429 Too Many Requests response, with a Retry-After header indicating when to retry.
• Per-Tenant Enforcement: Limits apply per tenant, regardless of how many API keys are issued. Issuing multiple tokens does not increase capacity.
• Real-Time Monitoring: API usage can be monitored from the “Admin Portal > Integrations > API Usage” section.

​

🛡️ Authentication & Token Management

• You can issue multiple API keys per tenant to support different integrations.
• All keys share the same cumulative limit based on the subscription tier.
• For authentication details, see API Authentication.

​

🔁 Retry Strategy

When receiving a 429 Too Many Requests response:

• Respect the Retry-After header (in seconds).
• Implement exponential backoff with jitter to prevent synchronized retry loops.
• Example 429 response body:

{
  "status": 429,
  "error": "Too Many Requests",
  "message": "Monthly API limit exceeded. Contact support to upgrade your plan.",
  "retry_after": 60
}

​

🧪 Development & Testing Environments

If you require a non-production environment for development or testing, contact support to request a sandbox tenant. Usage in development environments is isolated and does not count toward production API quotas. For questions about rate limits or to discuss higher-tier options, contact your Aptly account representative or support.