<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: API handling capacity in Discuss Dropbox Developer &amp; API</title>
    <link>https://www.dropboxforum.com/t5/Discuss-Dropbox-Developer-API/API-handling-capacity/m-p/450843#M1470</link>
    <description>&lt;P&gt;&lt;SPAN&gt;The Dropbox API does have a general rate limiting system, but we don't have any specific numbers documented (though they're relatively generous). Further, the limits operate on a per-user basis. That being the case, you usually don't need to worry about hitting it in normal use.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Also note that not all 429s and 503s indicate explicit rate limiting, but in any case that you get a 429 or 503 the best practice is to retry the request, respecting the Retry-After header if given in the response, or using an exponential back-off, if not.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;You can find some more information in &lt;A href="https://www.dropbox.com/lp/developers/reference/dbx-performance-guide" target="_self"&gt;the Performance Guide&lt;/A&gt;.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 04 Sep 2020 14:41:36 GMT</pubDate>
    <dc:creator>Greg-DB</dc:creator>
    <dc:date>2020-09-04T14:41:36Z</dc:date>
    <item>
      <title>API handling capacity</title>
      <link>https://www.dropboxforum.com/t5/Discuss-Dropbox-Developer-API/API-handling-capacity/m-p/450777#M1469</link>
      <description>&lt;P&gt;Hi, i am doing a POC project to leverage dropbox store and API provided, to exchange some real time data file. I am thinking to get a client application call dropbox api every couple seconds (or more high frequency) , to verify any change of those data files.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;What's the maxium frequency and amount of API call per every user account dropbox can support ? Is there any limitation ?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;thx.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 04 Sep 2020 17:45:17 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Discuss-Dropbox-Developer-API/API-handling-capacity/m-p/450777#M1469</guid>
      <dc:creator>autratec</dc:creator>
      <dc:date>2020-09-04T17:45:17Z</dc:date>
    </item>
    <item>
      <title>Re: API handling capacity</title>
      <link>https://www.dropboxforum.com/t5/Discuss-Dropbox-Developer-API/API-handling-capacity/m-p/450843#M1470</link>
      <description>&lt;P&gt;&lt;SPAN&gt;The Dropbox API does have a general rate limiting system, but we don't have any specific numbers documented (though they're relatively generous). Further, the limits operate on a per-user basis. That being the case, you usually don't need to worry about hitting it in normal use.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Also note that not all 429s and 503s indicate explicit rate limiting, but in any case that you get a 429 or 503 the best practice is to retry the request, respecting the Retry-After header if given in the response, or using an exponential back-off, if not.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;You can find some more information in &lt;A href="https://www.dropbox.com/lp/developers/reference/dbx-performance-guide" target="_self"&gt;the Performance Guide&lt;/A&gt;.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 04 Sep 2020 14:41:36 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Discuss-Dropbox-Developer-API/API-handling-capacity/m-p/450843#M1470</guid>
      <dc:creator>Greg-DB</dc:creator>
      <dc:date>2020-09-04T14:41:36Z</dc:date>
    </item>
  </channel>
</rss>

