Rate Limits
Current limits and future rate limiting plans for the Flow Myna API.
Current Limits
| Limit Type | Value | Notes |
|---|---|---|
| Batch Size | 100 events/objects | Per batch request |
| Request Rate | No hard limit | Be reasonable; abuse may be restricted |
| Event Name Length | 1-200 characters | Validated on every request |
| Object Type Length | 1-100 characters | Validated on every request |
| Object ID Length | 1-500 characters | Validated on every request |
Currently no request rate limit. We trust our users to be reasonable. If you're planning to send millions of events, please contact us first so we can ensure optimal performance for your use case.
Planned Rate Limits
We're planning to implement the following rate limits in a future release:
| Limit | Planned Value | Scope |
|---|---|---|
| Requests per minute | 1,000 | Per API key |
| Events per day | Varies by plan | Per workspace |
| Concurrent connections | 50 | Per API key |
Rate Limit Headers (Future)
When rate limits are implemented, responses will include these headers:
X-RateLimit-Limit: 1000
Maximum requests per minute
X-RateLimit-Remaining: 950
Requests remaining in current window
X-RateLimit-Reset: 1705315200
Unix timestamp when the rate limit resets
Handling Rate Limits
If you're rate limited (429 status), implement exponential backoff:
- 1. Read the
X-RateLimit-Resetheader - 2. Wait until that timestamp before retrying
- 3. Or use exponential backoff: 1s, 2s, 4s, 8s...
- 4. Add jitter to prevent thundering herd
Our SDKs handle this automatically. The Python and Node.js SDKs include built-in rate limit handling with intelligent backoff.
Need Higher Limits?
If your integration requires higher rate limits:
- Contact us — We can discuss enterprise options
- Use batching — Send up to 100 events per request
- Optimize timing — Spread requests over time