We’re Still Here to Help (Even Over the Holidays!) - find out more here.
Forum Discussion
yanjobin
4 years agoExplorer | Level 3
Dropbox API suddenly malfunctionning
Hello,
We have been using the Dropbox api in our application for a couple years now and it has always worked flawlesly.
Since about last week, the list_folder endpoint is no longer returning ...
Greg-DB
Dropbox Community Moderator
4 years agoIts sounds like your team recently switched to the "team space" configuration. By default, API calls operate in the "member folder" of the connected account, not the "team space", so you wouldn't see anything in the team space when using the API by default. You can configure API calls to operate in the "team space" instead though. To do so, you'll need to set the "Dropbox-Api-Path-Root" header. You can find information on this in the Team Files Guide.
- yanjobin4 years agoExplorer | Level 3
Configuring the api to operate in the team space using the "Dropbox-Api-Path-Root" header fixed the problem.
Thank you
- Jay P4 years agoNew member | Level 2
Greg...I connect to the DB API via Claris Connect.
I am experiencing the same problems as outlined in this post.
Do you have any information on how to update the "Dropbox-API-Path-Root Header" in Claris Connect?
- Greg-DB4 years ago
Dropbox Community Moderator
Jay P I can't offer support for Claris Connect itself, so I recommend referring to the documentation or support resources for Claris Connect. If Claris Connect doesn't already offer the ability to set the "Dropbox-API-Path-Root" header (or arbitrary headers such that you can specify "Dropbox-API-Path-Root"), the developer of Claris Connect will need to update it to support that.
- Jay P4 years agoNew member | Level 2
Greg,
Thank you very much for your quick response. I am reaching out to Clairs about this now. However, I was hoping to elaborate a bit more to ensure the fix is with Claris.
I connect to the DB API (via Claris Connect) to automate a Folder creation and create a Share (on the newly created Folder). It has worked perfectly for years…until the new DB update. “Team Spaces?”
Using my current code, the folder gets created in the correct directory, but when I reference the newly created folder’s path (to create a Share) I get the “invalid_root/” error returned.
This is what I send to create the folder…(and it works)
"--request POST --header \"Content-Type: application/json\" --data @$$JSONdata"
--------------------$$JSONdata Below--------------------------
JSONSetElement ( "{}" ;
["action" ; "script" ; JSONString] ;
["Path" ; $DBPath; JSONString] ;
["Folder Name" ; $JobFolder; JSONString]
)
However, I get this result when requesting the Share from the folder’s path:
"body":{2 items
"error_summary":string"invalid_root/."
"error":{2 items
".tag":string"invalid_root"
"invalid_root":{4 items
".tag":string"team"
"root_namespace_id":string"2986277024"
"home_namespace_id":string"152637445"
"home_path":string"/Jay Pif"
Do you think this is a Claris Connect issue?
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
The Dropbox Community team is active from Monday to Friday. We try to respond to you as soon as we can, usually within 2 hours.
If you need more help you can view your support options (expected response time for an email or ticket is 24 hours), or contact us on X, Facebook or Instagram.
For more info on available support options for your Dropbox plan, see this article.
If you found the answer to your question in this Community thread, please 'like' the post to say thanks and to let us know it was useful!