API access token expired

[farchacon]

Hola, estoy generando un token de acceso para Dropbox desde una cuenta en la que soy editor pero no soy propietario. Mi plan es Dropbox Basic de 2Gb.
Al igual que el caso anterior, me generó en principio un Token de 142 caracteres, pero luego generé un Token de 64 caracteres pero expira igual.
Que puede estar influyendo para que expire el Token??

Eso influye en el hecho que expire el Token??
Hello, I am generating an access token for Dropbox from an account where I am a publisher but not an owner. My plan is 2Gb Dropbox Basic.
Like the previous case, it initially generated a 142 character Token, but then I generated a 64 character Token but it expires anyway.
What could be influencing the expiration of the Token?

Does that influence the fact that the Token expires?

[Greg-DB]

If you're getting a "long-lived" access token (that is, it doesn't start with "sl." and is generally 64 characters long), that shouldn't expire by itself. 

There a number of different ways that a long-lived Dropbox API access token can become invalid though, including:

• the user or team admin can revoke all access tokens for an app by unlinking it on any of the following Dropbox web pages:
• the Connected apps page
• the Security checkup page
• the Team apps page on the Settings section of Business Admin console
• the team member’s page on the Members section of the Business Admin console
• any client with the access token can revoke the access token by calling /2/auth/token/revoke
• the GitHub-Dropbox token scanning partnership can revoke access tokens found publicly posted on GitHub
• if the app uses the "app folder" permission, the access token can effectively be disabled by deleting the app folder itself in the Dropbox account, via the Dropbox website or any client
• the app can be disabled
• the account that owns the app can be disabled
• the connected account can be disabled

Please review the above possibilities for information on why your token may be invalid. If the Dropbox API isn't behaving as expected, feel free to contact support by opening an API ticket.