<?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: Dropbox API v2 Rate Limiting in Dropbox API Support &amp; Feedback</title>
    <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Dropbox-API-v2-Rate-Limiting/m-p/250206#M14390</link>
    <description>Yes, the Dropbox API has a rate limiting system, for both the user and Business endpoints.&lt;BR /&gt;&lt;BR /&gt;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.</description>
    <pubDate>Mon, 30 Oct 2017 13:50:26 GMT</pubDate>
    <dc:creator>Greg-DB</dc:creator>
    <dc:date>2017-10-30T13:50:26Z</dc:date>
    <item>
      <title>Dropbox API v2 Rate Limiting</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Dropbox-API-v2-Rate-Limiting/m-p/250017#M14375</link>
      <description>&lt;P&gt;Is there a limit on the number of queries in "Business endpoints"?&lt;/P&gt;</description>
      <pubDate>Wed, 29 May 2019 09:17:46 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Dropbox-API-v2-Rate-Limiting/m-p/250017#M14375</guid>
      <dc:creator>uuuq</dc:creator>
      <dc:date>2019-05-29T09:17:46Z</dc:date>
    </item>
    <item>
      <title>Re: Dropbox API v2 Rate Limiting</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Dropbox-API-v2-Rate-Limiting/m-p/250206#M14390</link>
      <description>Yes, the Dropbox API has a rate limiting system, for both the user and Business endpoints.&lt;BR /&gt;&lt;BR /&gt;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.</description>
      <pubDate>Mon, 30 Oct 2017 13:50:26 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Dropbox-API-v2-Rate-Limiting/m-p/250206#M14390</guid>
      <dc:creator>Greg-DB</dc:creator>
      <dc:date>2017-10-30T13:50:26Z</dc:date>
    </item>
  </channel>
</rss>

