Broaden the scope of the User API
I would like to see more actions available to the users endpoint of the API. The ability to create, modify, delete, and audit logons for user accounts.
One use case - in an LDAP scenario, you might want to trim thousands of old users who lo longer exist in the LDAP environment (university)
Another use case - you want a user with necessary permissions to retrieve a user ID from the API in order to submit a ticket as that other user.

-
Cory Hatter commented
For anyone following this, in version 12.1, you can now get users:
GET /api/users/users
Kace has yet to update the API documentation, but it works for me.
-
Cory Hatter commented
If we were able to use the API to just at least get all users, with the following attributes, I think the overall usefulness of the API would increase significantly:
- owner_id
- user_name
- email
- full_nameThese are the attributes that are returned for user fields when you get an asset. WIthout being able to identify a user's owner_id, how can you assign them to an asset?