Skip to main content

​
Rate Limits

The Trigify API implements rate limiting to ensure fair usage and maintain service quality for all users.

​
Rate Limit Policy

Fixed window rate limit: 100 requests per 60 seconds
  • Window: 60 seconds
  • Limit: 100 requests per window
  • Scope: Per API key (authenticated) or per IP (unauthenticated)

​
How Rate Limiting Works

​
Identification

Rate limits are applied based on:
  1. API Key (primary) - Each API key gets its own rate limit bucket
  2. IP Address (fallback) - If no API key is provided, limits are applied per IP

​
Headers

Every API response includes rate limit information in the headers using the standard format:
  • RateLimit-Limit: The request limit per time window
  • RateLimit-Remaining: Number of requests remaining in current window
  • RateLimit-Reset: Seconds until the current window resets

​
Example Response Headers

RateLimit-Limit: 100
RateLimit-Remaining: 87
RateLimit-Reset: 13
Note: If you need the legacy X-RateLimit-* headers with Unix timestamps, this can be enabled by setting legacyHeaders: true in the middleware configuration.

​
Rate Limit Exceeded

When you exceed the rate limit, you’ll receive a 429 Too Many Requests response: 
{
  "success": false,
  "message": "Rate limit exceeded. Maximum 100 requests per minute allowed.",
  "error": "RATE_LIMIT_EXCEEDED"
}

​
Need Higher Limits?

If your use case requires higher rate limits, please contact our support team. We can discuss:
  • Custom rate limit tiers
  • Enterprise plans
  • Webhook-based alternatives
  • Bulk data export options
Contact us at [email protected] for more information.