title: How to handle name conflict with action in RESTful API
body: <p>RESTful API should be focused on resource and not action.
  However, when implementing RESTful on HTTP, due to the limited expressiveness of the HTTP methods, people add <code>[action]</code> to the end of the URL.</p>
  
  <p>e.g.:
  <a href="http://rebilly.github.io/ReDoc/#operation/findPetsByStatus" rel="nofollow noreferrer">http://rebilly.github.io/ReDoc/#operation/findPetsByStatus</a></p>
  
  <p><a href="https://developers.google.com/drive/api/v3/reference/" rel="nofollow noreferrer">https://developers.google.com/drive/api/v3/reference/</a></p>
  
  <p>(DELETE /files/trash and GET /files/generateIds)</p>
  
  <p>For API that the ID is defined by the user, the above design would lead to conflicts.</p>
  
  <p>i.e. user creating a pet <code>findPetsByStatus</code> or a file <code>trash</code> or <code>generateIds</code>.</p>
  
  <p>The API designer cannot prevent this from happening because we cannot foresee the future. i.e. we can't reserves all keywords that might be used as actions because the product evolves and changes over time.</p>
  
  <p>Under this circumstances, how to design an API so we won't run into such problem?</p>
  
  <p>I would like to follow OpenAPI spec but they disallow API with <code>/files?action=&lt;someAction&gt;</code></p>