<?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 DropBox app API usage in Discuss Dropbox Developer &amp; API</title>
    <link>https://www.dropboxforum.com/t5/Discuss-Dropbox-Developer-API/DropBox-app-API-usage/m-p/751867#M3921</link>
    <description>&lt;P&gt;So, we want to use DropBox to store some graphic assets of our app to reduce its size and let the users download more assets on demand. I do not care about the security of the assets at all (+ all access is read-only), so I plan to just use the generated API key directly in the app to communicate with DB in the background. Is this a valid approach/best practice? What are the rate limits? The assets are rather small (&amp;lt;50 MB in total), but I want it to scale well for high user counts.&lt;/P&gt;</description>
    <pubDate>Sat, 17 Feb 2024 06:19:38 GMT</pubDate>
    <dc:creator>User_1805491</dc:creator>
    <dc:date>2024-02-17T06:19:38Z</dc:date>
    <item>
      <title>DropBox app API usage</title>
      <link>https://www.dropboxforum.com/t5/Discuss-Dropbox-Developer-API/DropBox-app-API-usage/m-p/751867#M3921</link>
      <description>&lt;P&gt;So, we want to use DropBox to store some graphic assets of our app to reduce its size and let the users download more assets on demand. I do not care about the security of the assets at all (+ all access is read-only), so I plan to just use the generated API key directly in the app to communicate with DB in the background. Is this a valid approach/best practice? What are the rate limits? The assets are rather small (&amp;lt;50 MB in total), but I want it to scale well for high user counts.&lt;/P&gt;</description>
      <pubDate>Sat, 17 Feb 2024 06:19:38 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Discuss-Dropbox-Developer-API/DropBox-app-API-usage/m-p/751867#M3921</guid>
      <dc:creator>User_1805491</dc:creator>
      <dc:date>2024-02-17T06:19:38Z</dc:date>
    </item>
    <item>
      <title>Re: DropBox app API usage</title>
      <link>https://www.dropboxforum.com/t5/Discuss-Dropbox-Developer-API/DropBox-app-API-usage/m-p/752149#M3923</link>
      <description>&lt;P&gt;The API was designed with the intention that each user would link their own Dropbox account, in order to interact with their own files. While it is technically possible to always connect to just one account for all users, we do not officially support this, for various technical and security reasons.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The Dropbox API does have a general rate limiting system that applies to all account types, but we don't have specific rate numbers documented for that, and we cannot increase the limits for any particular app, user, or team. Apps should be written to handle these rate limit responses automatically. Also note that not all responses with a 429 or 503 status code indicate explicit rate limiting, but in any case that you get a response with 429 or 503 status code 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. I recommend referring to the &lt;A href="https://www.dropbox.com/developers/documentation/http/documentation#error-handling" target="_blank" rel="noopener noreferrer"&gt;error documentation&lt;/A&gt; and &lt;A href="https://developers.dropbox.com/error-handling-guide" target="_blank" rel="noopener noreferrer"&gt;Error Handling Guide&lt;/A&gt; for more information.&lt;/P&gt;</description>
      <pubDate>Mon, 19 Feb 2024 13:44:33 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Discuss-Dropbox-Developer-API/DropBox-app-API-usage/m-p/752149#M3923</guid>
      <dc:creator>Greg-DB</dc:creator>
      <dc:date>2024-02-19T13:44:33Z</dc:date>
    </item>
  </channel>
</rss>

