You might see that the Dropbox Community team have been busy working on some major updates to the Community itself! So, here is some info on what’s changed, what’s staying the same and what you can expect from the Dropbox Community overall.
Forum Discussion
API delete by id:# via CURL
In one script in my FileMaker database solution, I upload a file to a constructed path, then save the unique id:xxxxxxxxxxxxxxxx number for that record, to tie the record to the file in the DropBox d...
Wookiee, The question of mine was rhetoric! I hoped it'll direct you. Ok... can you see the difference of your 2 posts and figure out alone what's different and wrong or...?
PS: Everywhere some path can be used, the equivalent id can be used too. Even more a hybrid form may be used too: id of a folder followed by a relative path. In all cases that's NOT the issue (I assume the id is correct).
I just took the code section from the dev API example... here are the args that is getting sent by FileMaker using it's "Insert from URL" script step:
-X POST
--header "Content-Type: application/json"
--header "Authorization: Bearer <redacted>"
--header "Dropbox-API-Arg: {\"path\":\"id:m5ktIrz8BXoAAAAbAAAASg\"}"
--dump-header
Wookiee, The question of mine was rhetoric! I hoped it'll direct you. Ok... can you see the difference of your 2 posts and figure out alone what's different and wrong or...?
PS: Everywhere some path can be used, the equivalent id can be used too. Even more a hybrid form may be used too: id of a folder followed by a relative path. In all cases that's NOT the issue (I assume the id is correct).
Not quite there yet, but you have me on the right path, I think...
iNeilDropbox Engineer
Hello Wookiee,
The error "Unexpected HTTP headers: 'Dropbox-Api-Arg'" indicates that the HTTP request you sent includes a header that the server is not expecting or does not recognize, as mentioned by Здравко. For example, --header "Dropbox-API-Arg: {\"path\":\"id:m5ktIrz8BXoAAAAbAAAASg\"}".
Please note that the /2/files/upload and /2/files/delete_v2 endpoints have different formats when including parameters. The /2/files/upload endpoint uses the header "Dropbox-API-Arg," while the /2/files/delete_v2 endpoint uses the request body data. Below is an example of how to implement the /2/files/delete_v2 endpoint using the request body data via cURL.curl -X POST \ --header "Authorization: Bearer " \ --header "Content-Type: application/json" \ --data "{\"path\":\"id:m5ktIrz8BXoAAAAbAAAASg\"}" \ https://api.dropboxapi.com/2/files/delete_v2Thank you both! The following worked perfectly in FileMaker to delete the file. Putting this here for anyone who might need it.
"-X POST" & ¶ & " --header \"Content-Type: application/json\"" & ¶ & " --header \"Authorization: Bearer " & $authToken & "\"" & ¶ & " --data \"" & $dropboxArgJSON & "\"" & ¶ & "--dump-header $responseHeaders"
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
