<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[getCandleData rate-limit continues at very low request frequency - backend telemetry check required]]></title><description><![CDATA[<p dir="auto">Hi SmartAPI Team,<br />
We are still consistently receiving rate-limit errors on the Historical Candle API (getCandleData) even though our request frequency is very low and requests are spaced minutes apart.<br />
Recent failures on 6 Oct 2026 (UTC) occurred at approximately:</p>
<ul>
<li>06:22:14</li>
<li>06:26:17</li>
<li>06:31:28</li>
<li>06:32:32</li>
<li>06:34:35<br />
The error is:<br />
DataException: exceeding access rate<br />
Important observations:</li>
<li>Requests are not being sent in bursts.</li>
<li>We have conservative client-side rate limiting and cooldown handling enabled.</li>
<li>Quote/authentication APIs are working.</li>
<li>The issue appears specific to getCandleData.</li>
<li>Even isolated candle requests have sometimes been rejected.</li>
<li>The application is running in paper mode only; no live order execution is involved.<br />
Could you please check whether there is any API-key, account-level, IP-level, or backend historical-data throttle/restriction affecting our account?<br />
Please also confirm whether the currently documented getCandleData limits are being enforced differently on the backend.<br />
We can provide the exact request payload and timestamps if required, but we will not share authentication tokens or API secrets publicly.<br />
Thanks.</li>
</ul>
]]></description><link>https://smartapi.angelone.in/smartapi/forum/topic/5692/getcandledata-rate-limit-continues-at-very-low-request-frequency-backend-telemetry-check-required</link><generator>RSS for Node</generator><lastBuildDate>Mon, 12 Oct 2026 18:40:47 GMT</lastBuildDate><atom:link href="https://smartapi.angelone.in/smartapi/forum/topic/5692.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 06 Oct 2026 06:43:29 GMT</pubDate><ttl>60</ttl></channel></rss>