6.3.6 Pro - api broken + User Feedback As I Go + Conclusion

I noticed that there isn’t a way to browse snapshots using the API, would be nice if that information is being exposed via the API as well.

Also exposing the notifications would be greatly appreciated. It’s now only possible to get the amount of new notifications (undocumented), but I didn’t encounter a way to retrieve the actual notifications themselves.

the get events method returns the events but sometimes a description is missing (undefined).
For now I encountered it with the etypes:
repo-create and
repo-delete

PERMISSION FAULT: Error in getting File History information:

When a user tries to get the file history of a file which is read-only the API returns forbidden, although in Seahub the same information can be accessed perfectly fine.

This should be fixed so a user that has read-only access to a file can still read the file history via the API as intended

It seems that the access log of a file is not exposed via the API, would be nice if it was :slight_smile:

This one is annoying: when trying to open a file using OWA, it always returns {"error_msg":"path invalid."}

As soon as I use an incorrect filepath it says: {"error_msg":"File /subfolder/DOESNTEXIST.docx not found."}

The path I provide is 100% correct, there are no entries in any of the logs about this failed API call and yet I never get the response I’m looking for…

Manual: https://manual.seafile.com/develop/web_api_v2.1.html#view-file-through-owa

I tried all the curl examples, making sure they are exactly the same (only with my details) and ran it on the command line, still same result :frowning:

In addition, OpenOffice runs perfectly fine using Seahub

The recursive dir structure seafile returns is very impractical.
You’d expect some kind of recursive array as in

Library Name
___subfolder
______another subfolder
______subsubfolder
___subfolder

Instead, it just returns a flat list as such:

Library Name
subfolder
another subfolder
subsubfolder
subfolder

with a parent field. It’s really impractical to loop over a flat list and make a tree out of it in HTML

List Directory Entries
GET https://cloud.seafile.com/api2/repos/{repo-id}/dir/
t (optional): If set t argument as f, will only return file entries, and d for only dir entries.
recursive (optional): If set t argument as d AND recursive argument as 1, return all dir entries recursively

Documentation error: there seem to be functions to handle library trash, none of them are listed in the index at the top of the manual

It would be great if the search results return whether the library the file is in is encrypted or not.

https://cloud.seafile.com/api2/search/

Hmm, on second thought, it is stated that files in encrypted libraries are not indexed. Then why is there a search result coming back from one :slight_smile:

EDIT: same goes for starred results, would like to know if repo it’s from is encrypted or not

Starred files that you no longer have access to (e.g. when shared library is unshared) still show up in the “get all starred files” list:

https://cloud.seafile.com/api2/starredfiles/

IF you want to download mulitple files/folders but only provide dirents one file it says folder not found:and refuses to create the zip (no token)

GET https://cloud.seafile.com/api/v2.1/repos/{repo-id}/zip-task/?parent_dir={parent_dir}&dirents={dir,file}

However, you can provide a single folder, just not a single file

I’ve gone through most of the API and here are my Feature requests:

This will conclude this topic for me. I hope someone at seafile takes a look at the above topic :slight_smile: