<?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 API limits on RPC endpoints in Dropbox API Support &amp; Feedback</title>
    <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/API-limits-on-RPC-endpoints/m-p/334768#M19535</link>
    <description>&lt;P&gt;As per the Dropbox API doc, there limits to the API calls, but Dropbox does not wish to disclose any info on limitations.&lt;/P&gt;&lt;P&gt;I understand that there might be daily/monthly quota on upload/download APIs, but what are the limitations on RPC endpoints?&amp;nbsp; The reason I ask this is because, I will be doing a complete scan of pretty large Dropbox Business accounts (Thousands of members with millions of folders). Listing each folder at a time will be very time consuming and may even take days, so I plan to list multiple folders simulataneously and wanted to take advice on limits on number of concurrent list_folder requests. I ran a few tests and the behaviour was inconsistent. That is, at times I was able to list 10 folders concurrently while other times I get '429 too many requests' when trying to list 3 folders concurrently.&lt;/P&gt;</description>
    <pubDate>Wed, 29 May 2019 09:07:19 GMT</pubDate>
    <dc:creator>rk90</dc:creator>
    <dc:date>2019-05-29T09:07:19Z</dc:date>
    <item>
      <title>API limits on RPC endpoints</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/API-limits-on-RPC-endpoints/m-p/334768#M19535</link>
      <description>&lt;P&gt;As per the Dropbox API doc, there limits to the API calls, but Dropbox does not wish to disclose any info on limitations.&lt;/P&gt;&lt;P&gt;I understand that there might be daily/monthly quota on upload/download APIs, but what are the limitations on RPC endpoints?&amp;nbsp; The reason I ask this is because, I will be doing a complete scan of pretty large Dropbox Business accounts (Thousands of members with millions of folders). Listing each folder at a time will be very time consuming and may even take days, so I plan to list multiple folders simulataneously and wanted to take advice on limits on number of concurrent list_folder requests. I ran a few tests and the behaviour was inconsistent. That is, at times I was able to list 10 folders concurrently while other times I get '429 too many requests' when trying to list 3 folders concurrently.&lt;/P&gt;</description>
      <pubDate>Wed, 29 May 2019 09:07:19 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/API-limits-on-RPC-endpoints/m-p/334768#M19535</guid>
      <dc:creator>rk90</dc:creator>
      <dc:date>2019-05-29T09:07:19Z</dc:date>
    </item>
    <item>
      <title>Re: API limits on RPC endpoints</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/API-limits-on-RPC-endpoints/m-p/334914#M19537</link>
      <description>&lt;P&gt;The Dropbox API does have a rate limiting system, but we don't have any specific numbers documented. For reference though, the limits operate on a per-user basis.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;However, 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. (Generally the window isn't more than a few minutes.) T&lt;SPAN&gt;he rate limiting system and parameters are subject to change, so this strategy is preferred as it produces a more dynamic way of handling rate limiting, as opposed to relying on a hard-coded number.&amp;nbsp;&lt;/SPAN&gt;You should also check the response body for a specific error message.&lt;/P&gt;
&lt;P&gt;There are also some special cases that can produce rate limiting responses without excessive amounts of calls. For instance, with list_folder, some of the special cases that you might encounter:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;If certain file metadata is not yet available at the time of the API call (e.g., for new files), you'll get a 429 and will need to call back after the (generally very short, on the order of seconds) delay indicated in the Retry-After header.&lt;/LI&gt;
&lt;LI&gt;If y&lt;SPAN&gt;ou make multiple identical /2/files/list_folder[/continue] calls simultaneously (e.g., for the same user and folder), you'll get a 429 back. For those, avoid sending the duplicate calls.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 20 Mar 2019 15:33:45 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/API-limits-on-RPC-endpoints/m-p/334914#M19537</guid>
      <dc:creator>Greg-DB</dc:creator>
      <dc:date>2019-03-20T15:33:45Z</dc:date>
    </item>
  </channel>
</rss>

