Fair Usage & Rate Limiting Policy

1. Policy Overview

CapEngage implements fair usage policies and rate limits to ensure equitable resource allocation, prevent abuse, and maintain service quality for all customers.

This policy outlines the limits that apply to different subscription tiers and the consequences of exceeding these limits.

2. API Rate Limits

Rate limits are applied per API key. Exceeding limits results in HTTP 429 (Too Many Requests) responses.

3. Message Volume Limits

4. Storage Limits

5. API Usage

6. Rate Limit Headers

API responses include rate limit headers:

• X-RateLimit-Limit: Your rate limit
• X-RateLimit-Remaining: Requests remaining in current window
• X-RateLimit-Reset: Unix timestamp when limit resets
• Retry-After: Seconds to wait before retrying (on 429)

7. Exceeding Limits

7.1 Soft Limits

For soft limits (message volume, storage):

• Warning notifications at 80% of limit
• Service continues beyond limit with overage charges
• Overage charges apply per unit (message, GB)

7.2 Hard Limits

For hard limits (API rate limits):

• Requests are rejected with HTTP 429
• Client must implement exponential backoff
• No overage charges, requests simply fail

7.3 Abuse Prevention

Accounts that consistently abuse limits may be throttled or suspended.

8. Increasing Limits

To request higher limits:

• Upgrade to a higher plan tier
• Contact sales@capengage.com for custom Enterprise limits
• Purchase additional credits or add-ons