New 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.