Documentation v2.4.1

API Rate Limits & Throttling Policy

Rate limits ensure fair usage, system stability, and optimal performance across all Aevum Zenth public APIs, webhooks, and streaming endpoints. This page details tier-based limits, header specifications, retry strategies, and best practices for production integrations.

Tier-Based Limits

Rate limits are applied per API key and evaluated independently across regional API gateways. Limits reset at fixed intervals and cannot be carried over.

Subscription Tier	Requests / Minute	Requests / Day	Burst Allowance	Webhook / Streaming
Free / Sandbox	30	5,000	±15%	Disabled
Pro	120	150,000	±20%	Up to 5 concurrent
Business	500	2,000,000	±25%	Up to 25 concurrent
Enterprise	Custom / Unlimited	Dedicated allocation	Configurable	Unlimited

ℹ️

Note: Webhooks and WebSocket/streaming connections are not subject to standard REST rate limits but have separate concurrency and payload size constraints. Contact your account manager for tier adjustments.

Response Headers

Every API response includes standard rate limit headers to help clients track usage in real-time:

X-RateLimit-Limit: 120
X-RateLimit-Remaining: 84
X-RateLimit-Reset: 1698245400
Retry-After: 12 (only present on 429)

X-RateLimit-Limit: Maximum requests allowed in the current window.
X-RateLimit-Remaining: Requests left before the window resets.
X-RateLimit-Reset: Unix timestamp when the quota resets.
Retry-After: Seconds to wait before retrying (only on 429).

Handling Rate Limit Errors

When the rate limit is exceeded, the API returns a 429 Too Many Requests status code with a structured JSON body:

{
  "status": 429,
  "error": "rate_limit_exceeded",
  "message": "You have exceeded the allowed request quota. Please retry after the specified interval.",
  "retry_after": 14,
  "reset_at": 1698245400
}

Recommended Retry Strategy

Implement exponential backoff with jitter to prevent thundering herd effects:

// Pseudocode: Exponential backoff with jitter
delay = base_delay * (2 ^ attempt_count)
jitter = random(0, delay / 2)
wait_time = min(delay + jitter, max_delay)

// Always respect Retry-After header if present
if response.headers.has("Retry-After"):
    sleep(response.headers["Retry-After"])
    return

⚠️

Important: Do not retry synchronous requests faster than the Retry-After value. Repeated violations may trigger temporary key suspension (typically 60s–5min) to protect gateway infrastructure.

Best Practices

Cache Responses: Use ETag and Cache-Control headers to reduce redundant calls.
Batch Operations: Prefer bulk endpoints (POST /v2/batch) over sequential individual requests.
Pagination: Use cursor-based pagination instead of offset/limit to minimize round trips.
Graceful Degradation: Design clients to handle 429 without breaking critical workflows. Queue non-essential requests.
Distributed Systems: Centralize API key usage in a single gateway or use consistent hashing to avoid cross-node limit collisions.

Requesting Limit Increases

Need higher throughput for production workloads, batch processing, or real-time integrations? Enterprise and custom tiers support dedicated rate limit profiles, dedicated gateway instances, and SLA-backed guarantees.

Scale Your Integration

Upgrade your plan or speak with our API solutions team to configure custom limits, webhook scaling, and dedicated support.

Request Limit Increase → View Pricing Tiers

Support & Status

Rate limit configurations may change during major platform updates or regional gateway migrations. Always check the API Status Dashboard for real-time gateway health and incident reports.

For technical inquiries, integration reviews, or SLA requests, contact:

Email: api-support@aevumzenth.com
Portal: https://developers.aevumzenth.com/dashboard
Incidents: status.aevumzenth.com