Research completness of API bindings.

[matejak]

1. Research what is the extent of REST API that is available. Collaborate with Nextcloud devs / doc writes if necessary.
2. Ditto for key enterprisey addon apps.
3. Make some sort of easily editable table, make sure that it is part of the automatic docs generation (see also Create standard documentation on readthedocs.org #1)

[danil-topchiy]

OCS capabilites API:
https://docs.nextcloud.com/server/13/developer_manual/client_apis/OCS/index.html#capabilities-api (#14)

Official apps with REST API:
https://github.com/nextcloud/activity/blob/master/docs/endpoint-v2.md (#15)
https://github.com/nextcloud/notifications/blob/master/docs/ocs-endpoint-v2.md (#16)
https://github.com/nextcloud/notifications/blob/5a2d3607952bad675e4057620a9c7de8a7f84f0b/docs/push-v3.md
https://docs.nextcloud.com/server/14/admin_manual/configuration_user/user_auth_ldap_api.html (#17)
https://github.com/nextcloud/gallery/wiki/RESTful-API (BETA QUALITY)

Unofficial apps from app store with REST API:
https://github.com/nextcloud/bookmarks

WebDAV Directory API:
https://docs.nextcloud.com/server/14/user_manual/files/access_webdav.html

[matejak]

Great, I like the overview here. I propose this approach:
Let's make a script that generates a RST-formatted table in form
API name, link to the API definition | implementation status (not implemented, partial, OK).
The script could render a hand-crafted JSON into a RST file containing solely the table that could be included somewhere in the documentation. The JSON and could be tracked in the repository and the generation of RST could be part of the documentation Makefile. We could use some trick to trigger the build from conf.py, so documentaion on readthedocs would be also up-to-date, as they bypass the project's Makefile.
For the near future, the top priority APIs are ones to do with:

• Files
• Groups
• Users
• Group Folders
• Notifications

[danil-topchiy]

It totally makes sense, thanks, will do the table.

By Files api you mean WebDAV (https://docs.nextcloud.com/server/14/user_manual/files/access_webdav.html) ?

[matejak]

To be honest, I assumed that there is an API for manipulating files and the corresponding metadata. Don't be affraid to study the Nextcloud REST API and become the expert! I see that webdav is the key member of this equation, so it is great that you have started doing it!

[matejak]

Done, see https://nextcloud-api.readthedocs.io/en/latest/introduction.html#which-api-does-it-support