We're making changes to the Community, so you may have received some notifications - thanks for your patience and welcome back. Learn more here.
Forum Discussion
Unable to retrieve folder revisions through /metadata using rev parameter.
When I attempt to retrieve a folder's specific revision through /metadata I get back an error indicating that the rev is invalid or outdated.
The documentation is worded such that this seems to be ...
I just did some testing with the /revisions and /restore calls. I'm getting back a path not found when trying to reference a folder.
Here is the /revisions request and response.
Request:
GET https://api.dropbox.com/1/revisions/auto/Test?rev_limit=1000 HTTP/1.1
Authorization: Bearer ___________________________
Accept: application/json, application/xml, text/json, text/x-json, text/javascript, text/xml
User-Agent: RestSharp/104.4.0.0
Host: api.dropbox.com
Accept-Encoding: gzip, deflate
Response:
HTTP/1.1 404 Not Found
Server: nginx
Date: Thu, 14 May 2015 18:13:02 GMT
Content-Type: application/json
Connection: keep-alive
Content-Length: 35
{"error": "Path '/Test' not found"}
The API is a little clearer on this one. Though it doesn't explicitly say /revisions and /restore only work with files, it does use the word file any time it references the items being retrieved rather than the usual "file or folder". From this, it appears that the Dropbox API only supports using revs with files. If this is indeed the case though, why do folders have revs that get returned? And how would you go about restoring a deleted folder?
