title: REST API design: one endpoint with if/else logic or two separate role based endpoints
body: <p>I have an API design/versioning conundrum.
  Let's say I have an endpoint <code>/api/customers</code> which GETs all customers (ignore pagination). There's a twist though: if a regular <code>user</code> accesses this endpoint, they will only get the customers created by that user and no one else (I can check the access token and the sub field to determine who sent the request). Other usecase: if an <code>admin</code> accesses this endpoint, they should get ALL customers, regardless of who acquired them.</p>
  
  <p>Now my question is from an API design perspective: is it better to have an <code>if/else</code> role check within the API controller itself to determine do I return ALL (admin) customers or specific (user) customers, OR should I differentiate between endpoints for the user and admin? I.e. admin only endpoint for all customers would be <code>/api/admin/customers</code> and regular users can still access their <code>/api/customers</code>?</p>