cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Want to know what we learned at IBC? Check out our learnings on media, remote working and more right here.

Dropbox API Support & Feedback

Find help with the Dropbox API from other developers.

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Re: Dropbox Chooser - 403 Error Returned

Dropbox Chooser - 403 Error Returned

djtaylor8
New member | Level 2
Go to solution

We recently incorporated the Dropbox Chooser widget into our application so that users could select files from their Dropbox account and upload them directly to our server. Note that as part of our configuration, we set up the link type to be direct, so we fetch the file using the link returned from Dropbox. However, we are consistently getting 403 errors returned and I'm not quite sure how to remediate. Please let me know if you have any suggestions.

1 Accepted Solution

Accepted Solutions

Greg-DB
Dropbox Staff
Go to solution

This can occur due to link restrictions that can be set that prevents links from being accessed outside of members of the shared folder or the team.

 

By default, links are accessible without authentication, but team admins can optionally enforce additional access controls on links for their team members in general, which also apply to the links as returned by the Chooser. Likewise, link restrictions can be set on specific shared/team folders.

 

Unfortunately, we don't have a good solution right now for using the Chooser in cases where restrictions on links are set like this, but I'll send this along to the team to look into how to potentially improve this.

 

That being the case, one alternative right now is to use the HTTP API instead, where /2/files/download isn't subject to the same restrictions as the authorized access token allows you direct access to the user's account. That would be substantially more work to implement though.

View solution in original post

2 Replies 2

Greg-DB
Dropbox Staff
Go to solution

This can occur due to link restrictions that can be set that prevents links from being accessed outside of members of the shared folder or the team.

 

By default, links are accessible without authentication, but team admins can optionally enforce additional access controls on links for their team members in general, which also apply to the links as returned by the Chooser. Likewise, link restrictions can be set on specific shared/team folders.

 

Unfortunately, we don't have a good solution right now for using the Chooser in cases where restrictions on links are set like this, but I'll send this along to the team to look into how to potentially improve this.

 

That being the case, one alternative right now is to use the HTTP API instead, where /2/files/download isn't subject to the same restrictions as the authorized access token allows you direct access to the user's account. That would be substantially more work to implement though.

djtaylor8
New member | Level 2
Go to solution

Thank you for the response! We found this to be the case with a shared team folder and needed to adjust the link sharing permissions accordingly. 

Need more support?