JAVA API Shared Link Access Denied

Hi softwaremedicalshare,

Did you ensure "sharing.write" permission for your application (both in Application console and on token generation)?

Hope this gives right direction.

softwaremedicalshare It sounds like your links may currently be banned on your account. That would cause this error. (This doesn't sound like a scopes issue; that would be a different error message.)

You can find more information on link bans here: https://help.dropbox.com/files-folders/share/banned-links 

Hi @Здравко, 

Have this options in Application "Permissions" tab

Account info

   account_info.write off

   account_info.read is on

Files and folders

   files.metadata.write is on

   files.metadata.read is on

   files.content.write is on

   files.content.read is on

Collaboration

   sharing.write is on

   sharing.read is on

   file_request.write is on

   file_request.read is on

   contacts.write is on

Token generation was done with

   Allow public clients (Implicit Grant & PKCE) is Allow
   Access token expiration is No expiration

I generate a new token yesterday thinking it could be the issue, but issue remains. I can upload files, files is perfectly stored in dropbox but cannot generate shared link within the application. Also I just test and my username cannot create a shared link. Dropbox page says: "You do not have permissions to create a link for the file" (I just translate it maybe is not the exact message in English)

softwaremedicalshare It looks like our comments just crossed. Be sure to check out my message here.

Hi @Greg-DB, 

The issue you address sound more like a "banned link" i mean, something that existed before and suddenly it is banned for the reasons described in the link provided. The issue right now is that I cannot create new links for new files.

Thanks anyway

Hi softwaremedicalshare,

Just for clarity: When I mentioned "and on token generation", the meaning was for queried permissions there, not eventual token break!

When you have created your application you have declared the possible scopes this application can have access to. Seems your declaration covers "sharing.write" permission needed by 2/sharing/create_shared_link_with_settings. On token generation you should select a subset of all scopes of your application (could be all available/selected for the application or less). If you have forgot some scope here, even selected for the application, it'll not be available for the application instances! That's why just "generate a new token" in such a case (if it is) wouldn't solve anything. If missing (something which I suspected), you should add it to the list of scopes in your application code (or configuration). That's it.

By the way, it's most likely Greg-DB's proposal be the real issue.

softwaremedicalshare The link ban I referred to does apply to the functionality you're trying to use. I recommend contacting support if you have questions about the status of your account.