Current Situation:
The rest/api/3/user/search endpoint does not support filtering or excluding specific user types (for example, customers).

Problem:
As a result, additional logic is required on the client side to filter out unwanted user types after fetching the data. This increases code complexity, introduces potential for errors, and can negatively impact app performance.

Suggestion:
Adding support for filtering/excluding user types directly in the endpoint would simplify client implementations, reduce error risk, and improve performance.