There is some leftover endpoints from very early experiments with using the API for team components, but almost none of them are compatible with the default syntax for the REST API, which causes confusion, especially with the new landing page for the root endpoint (see #110).
We haven't considered this functionality recently, and there does seem to be strong use case for admins of existing installations to set up their teams with the API. So this should also implement a minimum viable product for such an operation.
For now, lets clean up the existing existing endpoints and implement the following:
This will exclude team users, team sites and roles as those are less likely to be bulk operations.
There is some leftover endpoints from very early experiments with using the API for team components, but almost none of them are compatible with the default syntax for the REST API, which causes confusion, especially with the new landing page for the root endpoint (see #110).
We haven't considered this functionality recently, and there does seem to be strong use case for admins of existing installations to set up their teams with the API. So this should also implement a minimum viable product for such an operation.
For now, lets clean up the existing existing endpoints and implement the following:
This will exclude team users, team sites and roles as those are less likely to be bulk operations.