SyncFlo AI
Limits

Rate Limiting

SyncFlo enforces rate limits to ensure fair usage and platform stability. Monitor your usage through response headers included in every API response.

Current Limits

API-key requests are rate-limited to 120 requests/minute per key.
Dashboard session requests are NOT rate-limited.
Window
120req/min
Per API key, rolling window

Response Headers

Every API response includes rate-limit headers so your application can track usage in real time.

HeaderDescription
X-RateLimit-LimitMaximum number of requests allowed per window (always 120).
X-RateLimit-RemainingNumber of requests remaining in the current window.
X-RateLimit-ResetUnix epoch timestamp (milliseconds) when the window resets.

Example Response Headers

HTTP Response Headers

HTTP/1.1 200 OK
Content-Type: application/json
X-RateLimit-Limit: 120
X-RateLimit-Remaining: 87
X-RateLimit-Reset: 1719734520000

Exceeding the Limit

When the rate limit is exceeded, the API returns a 429 Too Many Requests status with a Retry-After header indicating how many seconds to wait before retrying.

429 Response

HTTP/1.1 429 Too Many Requests
Retry-After: 12
Content-Type: application/json

{
  "error": "Rate limit exceeded. Retry after 12 seconds.",
  "code": "rate_limited"
}

Rate Limit Best Practices

Monitor X-RateLimit-Remaining headers and throttle requests before hitting the limit.
Implement exponential backoff when you receive a 429 response.
Use the Retry-After header value to determine the exact wait time.
Batch operations where possible to reduce the total number of API calls.
Use webhooks for real-time events instead of polling endpoints repeatedly.