The API user search was mainly an afterthought, so it could use some upgrades:
Remove implied "&action=search" parameter (there are no other actions)
Set default rows value to 10, as with normal search (currently it is set to 100000)
Remove error message for 0 results. 0 is a valid response, and users should just get an empty set, not a 404 error.
Harmonize the response format with normal search. Currently, it's just a different format—total has a different field name, search metadata is in a header field, results are in a users array instead of results, etc.
Implement full fielded search and resultFields, with sorting, range search, and export. Currently, only id can be searched on and resultFields is not allowed.
I think these are all design considerations except the last one, which probably needs a requirement or two.
The API user search was mainly an afterthought, so it could use some upgrades:
totalhas a different field name, search metadata is in aheaderfield, results are in ausersarray instead ofresults, etc.idcan be searched on and resultFields is not allowed.I think these are all design considerations except the last one, which probably needs a requirement or two.