NOVIX / Free tools
n8n API Rate Limit Planner
Estimate a conservative request pace, average concurrency and bounded retry delays before an external API starts returning 429s. / 외부 API의 429 오류를 줄이기 위한 보수적 호출 속도·평균 동시성·재시도 간격을 계산합니다.
Inputs / 입력
Planning output / 계산 결과
Safe average rate
48/min
Minimum average interval
1250 ms
Estimated average concurrency
1
Retry sequence
2s → 4s → 8s → 16s
How to use this / 적용 방법
- Keep steady-state traffic below the provider quota instead of waiting for 429s.
- When the API sends
Retry-After, treat it as the minimum retry delay. - Retry only transient failures such as 429 and selected 5xx responses; authentication or validation errors usually require a fix, not another attempt.
- Protect create/send/charge/update operations with idempotency so a timeout retry cannot duplicate the side effect.
This is a capacity-planning estimate, not a guarantee. Real limits can use sliding windows, burst rules, per-endpoint quotas, shared tenants or provider-specific concurrency controls.
Need implementation patterns?
Read the 429 / 5xx retry guide or use the Reliability Kit templates for retry boundaries, error handling and duplicate prevention.