n8n Public API Adds Per-Key Rate Limiting
Understand this story
n8n launched public API rate limiting in version 2.47.0: administrators can set a request cap for each API key, so a single runaway workflow hits that key's limit without blocking other teams on the same instance. The feature covers all plans and is available on both Cloud and self-hosted. Rate limiting is off by default and must be enabled by an administrator. Only requests through /api/v1 using an API key count toward the limit; requests from the n8n editor do not.
AI overview based on source reports · Updated 1 days ago
Coverage timeline
Follow the coverage to explore different perspectives.
- n8n BlogNew in n8n: Public API rate limits that keep every team on your instance running
n8n 2.47.0 introduces per-API-key public API rate limits, available on all plans for Cloud and self-hosted, with separate read and write limits across all endpoints and per endpoint. Clients receive 429 responses with Retry-After and rate-limit headers, and in multi-main setups every main shares one count per API key through Redis. Rate limiting is off by default and can be enabled via Settings > Policies > Public API Limits, the settings API, or environment variables, and works alongside idempotency keys (since 2.45.0) to make retries safe.
Activity for this story
- Current comparable activity
- 5
- Peak comparable activity
- 10Nov 13 19:00
- Change in the past 24 hours
- -50%
Trends compare the same fully observed participants, which may cover fewer participants than current activity. Move the pointer or tap the chart to inspect hourly activity; use the left and right arrow keys with a keyboard.