Same issue here — running a Nifty-options intraday bot polling getCandleData (FIVE_MINUTE) once every 5 minutes, ~0.003 req/s against the documented 3 req/s/client cap. Comparing the identical 09:15-10:35 window across three consecutive sessions: 12, then 17, then 27 rate-limit rejections, and the last two days both fully exhausted a 6-attempt retry budget on the very first request of the day, before any other call had been made. That makes six independent reports of this exact symptom now, across two different endpoints — candle data and order book — all well under documented limits: 5636/5637, 5611, 5625, 5595, 5560. I've put together a fuller writeup with the full data here: https://smartapi.angelbroking.com/smartapi/forum/topic/5639/getcandledata-rate-limit-false-positives-at-0-003-req-sec-six-independent-reports-zero-acknowledgment Would genuinely appreciate an actual look at the server-side telemetry rather than another "can't help with your code" response.

CARLOS GOMES ALEXANDRE NETO TOTAL ASSETS AVAILABLE US$ 1.8 BILLION

@S57010238 Since login AND placeOrder work but you still get AG8004, the key itself is fine — the failure is scoped to specific endpoints. Which call throws it (getCandleData / market data)? Two verified findings from debugging the same error family after the April migration: generateSession doesn't validate the API key at all, and endpoint groups validate scopes separately — so "logs in fine" (or even "orders work") proves nothing about the data endpoints. The migration replaced the old KEY TYPEs (Trading / Market Feed / Historical) with unified apps, but apps or keys that straddle the migration can still be rejected on some routes. Recreating the app fresh on the new portal fixed it in my case — note you may then hit "Primary static IP is already associated with another app", because deleted legacy apps don't release their registered IPs. Full write-up with the complete fix path + two extra gotchas (the Python SDK prints your API key into error logs; NSE Saturday DR-drill sessions serve mock candles as real data): https://smartapi.angelone.in/smartapi/forum/topic/5635/complete-fix-ag8004-invalid-api-key-after-successful-login-primary-static-ip-is-already-associated-with-another-app If you share which endpoint fails and when the app was created, happy to help narrow it down.

Facing same issue

@diljeets-0 Team What is your TAT to reply to queries.

@santokh3386 Dear @Nishanth_002 and @admin @admin1 Can anyone please help to understand the issue and resolve the same. thanks