<?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: Access Token 2 in Discuss Dropbox Developer &amp; API</title>
    <link>https://www.dropboxforum.com/t5/Discuss-Dropbox-Developer-API/Access-Token-2/m-p/736825#M3809</link>
    <description>&lt;P&gt;&lt;a href="https://www.dropboxforum.com/t5/user/viewprofilepage/user-id/1759968"&gt;@Adi4&lt;/a&gt;&amp;nbsp;Здравко is correct; Dropbox is no longer offering the option for creating new long-lived access tokens. Dropbox is now issuing short-lived access tokens (and optional refresh tokens) instead of long-lived access tokens. You can find &lt;A href="https://dropbox.tech/developers/migrating-app-permissions-and-access-tokens#updating-access-token-type" target="_blank" rel="noopener noreferrer"&gt;more information on this migration here&lt;/A&gt;.&lt;BR /&gt;&lt;BR /&gt;Apps can still get long-term access by requesting "offline" access though, in which case the app receives a "refresh token" that can be used to retrieve new short-lived access tokens as needed, without further manual user intervention. Refresh tokens do not expire automatically and can be used repeatedly. You can find more information in the &lt;A href="https://developers.dropbox.com/oauth-guide" target="_blank" rel="noopener noreferrer"&gt;OAuth Guide&lt;/A&gt; and &lt;A href="https://www.dropbox.com/developers/documentation/http/documentation#authorization" target="_blank" rel="noopener noreferrer"&gt;authorization documentation&lt;/A&gt;. There's a basic outline of processing this flow in &lt;A href="https://dropbox.tech/developers/using-oauth-2-0-with-offline-access" target="_blank" rel="noopener noreferrer"&gt;this blog post&lt;/A&gt; which may serve as a useful example.&lt;/P&gt;</description>
    <pubDate>Wed, 13 Dec 2023 15:14:23 GMT</pubDate>
    <dc:creator>Greg-DB</dc:creator>
    <dc:date>2023-12-13T15:14:23Z</dc:date>
    <item>
      <title>Access Token 2</title>
      <link>https://www.dropboxforum.com/t5/Discuss-Dropbox-Developer-API/Access-Token-2/m-p/736686#M3803</link>
      <description>&lt;P&gt;Hi Everyone !&lt;BR /&gt;I tried to generate long live Access Token form using URL and Code but I am not able to Get Access Token.&amp;nbsp;&lt;BR /&gt;Please Guide me to get access token&amp;nbsp;&lt;BR /&gt;&lt;a href="https://www.dropboxforum.com/t5/user/viewprofilepage/user-id/50413"&gt;@Greg&lt;/a&gt;&amp;nbsp;&amp;nbsp;&lt;a href="https://www.dropboxforum.com/t5/user/viewprofilepage/user-id/422790"&gt;@Здравко&lt;/a&gt;&amp;nbsp;.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 13 Dec 2023 06:41:43 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Discuss-Dropbox-Developer-API/Access-Token-2/m-p/736686#M3803</guid>
      <dc:creator>Adi4</dc:creator>
      <dc:date>2023-12-13T06:41:43Z</dc:date>
    </item>
    <item>
      <title>Re: Access Token 2</title>
      <link>https://www.dropboxforum.com/t5/Discuss-Dropbox-Developer-API/Access-Token-2/m-p/736714#M3805</link>
      <description>&lt;P&gt;As I already explained &lt;A href="https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Access-Token/m-p/736217/highlight/true#M32510" target="_blank" rel="noopener"&gt;here&lt;/A&gt;, there is no more long lived access token and don't know how to say it more clear. Such token was supported some time ago, but it's no more. Probably by mistake on some places in documentation this type of token still exists, but it's a mistake... nothing more! There is no way to get new long lived access token. That's why nobody could guide you - it's impossible. You have to use refresh token! Just don't forget it. That's it.&lt;/P&gt;</description>
      <pubDate>Wed, 13 Dec 2023 08:45:28 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Discuss-Dropbox-Developer-API/Access-Token-2/m-p/736714#M3805</guid>
      <dc:creator>Здравко</dc:creator>
      <dc:date>2023-12-13T08:45:28Z</dc:date>
    </item>
    <item>
      <title>Re: Access Token 2</title>
      <link>https://www.dropboxforum.com/t5/Discuss-Dropbox-Developer-API/Access-Token-2/m-p/736825#M3809</link>
      <description>&lt;P&gt;&lt;a href="https://www.dropboxforum.com/t5/user/viewprofilepage/user-id/1759968"&gt;@Adi4&lt;/a&gt;&amp;nbsp;Здравко is correct; Dropbox is no longer offering the option for creating new long-lived access tokens. Dropbox is now issuing short-lived access tokens (and optional refresh tokens) instead of long-lived access tokens. You can find &lt;A href="https://dropbox.tech/developers/migrating-app-permissions-and-access-tokens#updating-access-token-type" target="_blank" rel="noopener noreferrer"&gt;more information on this migration here&lt;/A&gt;.&lt;BR /&gt;&lt;BR /&gt;Apps can still get long-term access by requesting "offline" access though, in which case the app receives a "refresh token" that can be used to retrieve new short-lived access tokens as needed, without further manual user intervention. Refresh tokens do not expire automatically and can be used repeatedly. You can find more information in the &lt;A href="https://developers.dropbox.com/oauth-guide" target="_blank" rel="noopener noreferrer"&gt;OAuth Guide&lt;/A&gt; and &lt;A href="https://www.dropbox.com/developers/documentation/http/documentation#authorization" target="_blank" rel="noopener noreferrer"&gt;authorization documentation&lt;/A&gt;. There's a basic outline of processing this flow in &lt;A href="https://dropbox.tech/developers/using-oauth-2-0-with-offline-access" target="_blank" rel="noopener noreferrer"&gt;this blog post&lt;/A&gt; which may serve as a useful example.&lt;/P&gt;</description>
      <pubDate>Wed, 13 Dec 2023 15:14:23 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Discuss-Dropbox-Developer-API/Access-Token-2/m-p/736825#M3809</guid>
      <dc:creator>Greg-DB</dc:creator>
      <dc:date>2023-12-13T15:14:23Z</dc:date>
    </item>
  </channel>
</rss>

