title: REST API Endpoint Naming Conventions?
body: <p>I have an issue with naming endpoints in a REST api.</p>
  <p>Let's say you have a UI on the client side and in that UI is a table with a list of files. When tapping on a file it will proceed to download that selected one from the server. Additionally there is a button that when clicked will download all the files or selected files.</p>
  <p>So the endpoints on the API may be structured like so...</p>
  <ul>
  <li>[GET] Api/Files/{fileName}
  <ul>
  <li>Gets a single file by the file name provided in the route.</li>
  </ul>
  </li>
  <li>[GET] Api/Files
  <ul>
  <li>Gets a list of the files, including: FileName, Size, Type, etc...</li>
  </ul>
  </li>
  <li>[GET] Api/Files
  <ul>
  <li>Gets the files, returned as a ZIP file.</li>
  </ul>
  </li>
  </ul>
  <p>As you can see the issue is the conflict of endpoints with Api/Files. I would expect both endpoints to do what I have specified that they do. But one of them needs to change... I've thought about adding something to the end but mostly verbs come to mind. Any ideas on how the formatting could be done?</p>