Your workflow is unique 👨💻 - tell us how you use Dropbox here.
Forum Discussion
Leon_NAM
4 years agoHelpful | Level 5
API Call using Integromat returns error
Hey there,
I want to create an automated API Call to our company's Dropbox that creates a folder with only select user groups having access. To do that I am using the Dropbox "Make an API Call"...
Leon_NAM
4 years agoHelpful | Level 5
Hey there,
thanks for the detailed reply! Now I definetely understand why it's throwing an error. I am not making the app however it is a web-based integration software (https://www.integromat.com/) so it looks like the problem is that their app doesn't request "enough" access when you connect it to Dropbox.
UPDATE: I made some progress. The problem here is that integromat doesn't ask for the extended permissions until it needs them for one of the Dropbox preset modules they offer. As soon as you try to use one of them (e.g. Create Folder) it allows you to update the permissions of the app. It's a bit cumbersome but it might have worked (now I am getting a 409 instead of a 401 error which is probably due to missing permissions my account has)
Greg-DB
Dropbox Community Moderator
4 years agoThat's correct, a "missing_scope" error indicates that the access token being used isn't authorized with the particular scope needed to access that endpoint, and so the call is not allowed. You'd instead need to get an access token with that scope authorized.
A 409 error would indicate a different kind of endpoint-specific error. You should check the response body for more specific error information.
- Leon_NAM4 years agoHelpful | Level 5
Hey,
thanks for the replies. You are both right of course. Just saying "there is a [409] no_permission/.. error" is hardly enough information to go on. Sadly integromat does not supply any further information on the error...
My input is the same as last time:
URL/2/sharing/share_folderBody{ "path": "/not a machine cloud/projekte/2021/21012 - casefilm google barklaycard - acht - jm/test", "acl_update_policy": "editors", "force_async": false, "member_policy": "team", "shared_link_policy": "members", "access_inheritance": "no_inherit" }Dropbox API EndpointapiMethodPOSTHeadersKeyContent-TypeValueapplication/jsonDisable Dropbox API Path RootfalseAny idea where I could start looking to get to the bottom of this?
- Здравко4 years agoLegendary | Level 20
Leon_NAM wrote:
.... Just saying "there is a [409] no_permission/.. error" ...Hi Leon_NAM,
Yes, sometimes the error message isn't too verbose. 🤷 It's clear though that some permissions are missing. Do you able to share the same folder, using web interface, in context of the same account? 🤔 Are you (as account) the folder owner? Do you have rights to do that? Is some other shared folder within the one you are trying to share or does 'test' folder reside within a shared folder?
- Leon_NAM4 years agoHelpful | Level 5
Hey Здравко ,
thanks for the hint. I was using the /share_folder call on a folder that was created by another team member and in it the call was supposed to create a folder called 'test'. I wanted to take this out of the equation for now as it might be fixed if I give the Integromat app more permissions in the dropbox but I can't access those preferences right now.
So what I did to test the actual API call is I went into the root folder (a folder I most definetely own) and executed the program. I do get a new error here (which I would say is a success!) and it reads: "[400] Error in call to API function "sharing/share_folder": request body: could not decode input as JSON". Did I do something wrong in the body of the call?
Here's my input:
URL/2/sharing/share_folderBody{ "path": "/not a machine cloud/test", "acl_update_policy": "editors", "force_async": false, "member_policy": "team", "shared_link_policy": "members", "access_inheritance": "no_inherit"}Dropbox API EndpointapiMethodPOST--Headers:KeyContent-TypeValueapplication/json--
Disable Dropbox API Path RootfalseThanks for all your help!
About Dropbox API Support and Feedback
Get help with the Dropbox API from fellow developers and experts.
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!