Skip to main content
EngageFabric uses rate limiting to ensure fair usage and protect the platform from abuse.

Rate Limit Tiers

Rate Limit Headers

Every API response includes rate limit information:

Rate Limit Response

When you exceed the rate limit, you’ll receive a 429 Too Many Requests response:
The Retry-After header indicates how many seconds to wait:

Rate Limit Types

API Rate Limits

Applied per project API key:

IP Rate Limits

Applied globally per IP address:
Sharing API keys across multiple clients can quickly exhaust rate limits. Use one API key per deployment environment.

Event Ingestion Limits

Special limits for the /events endpoint: Events support burst capacity using a token bucket algorithm.

WebSocket Limits


Handling Rate Limits

Retry Strategy

Implement exponential backoff when rate limited:

Batch Requests

For events, use batch tracking to reduce API calls:

Monitor Usage

Track your rate limit usage via response headers:

Abuse Detection

EngageFabric monitors for abusive patterns:
  • Rapid repeated requests
  • Unusual event patterns
  • Coordinated attacks
Projects exhibiting abuse may be temporarily suspended.
If you believe you’ve been incorrectly rate limited, contact support with your requestId for investigation.

Increasing Limits

Need higher limits? Options include:
  1. Upgrade your tier: Higher tiers have increased limits
  2. Enterprise plan: Custom limits for your needs
  3. Temporary increase: Contact support for special events

Contact Sales

Need custom rate limits? Contact our sales team