title: PUT vs. POST when creating multiple resources that already have IDs
body: <p>I'm building an API where the majority of endpoints accept and return multiple resources. I'm having trouble determining whether to use POST or PUT requests.</p>
  
  <p>In my situation, resources are always created and identified outside of the API using UUIDs for identifiers. Since the resources already exist and are already identified, a PUT request seems appropriate. However, it would be impractical to include the UUID of each resource in the URI (the UUIDs are very long and there could be many resources in a single request).</p>
  
  <p>A POST request also seems appropriate because even though the resource is already identified with an ID, it does not yet exist in <em>our</em> database. Also, with POST requests, there is no expectation of having the IDs in the URI.</p>
  
  <p>Which would be the correct HTTP verb to use in this situation?</p>
  
  <pre><code> PUT /resources/1,2,3 ---&gt; Impractical due to the number of resources per request  
   PUT /resources ---------&gt; More practical but lacks IDs in the URI
  POST /resources ---------&gt; Possibly inaccurate verb since resource is already identified
  </code></pre>