RESTful way to create multiple items in one request

by

I believe that another correct way to approach this would be to create another resource that represents your collection of resources.
Example, imagine that we have an endpoint like /api/sheep/{id} and we can POST to /api/sheep to create a sheep resource.

Now, if we want to support bulk creation, we should consider a new flock resource at /api/flock (or /api/<your-resource>-collection if you lack a better meaningful name). Remember that resources don’t need to map to your database or app models. This is a common misconception.

Resources are a higher level representation, unrelated with your data. Operating on a resource can have significant side effects, like firing an alert to a user, updating other related data, initiating a long lived process, etc. For example, we could map a file system or even the unix ps command as a REST API.

I think it is safe to assume that operating a resource may also mean to create several other entities as a side effect.

More Related Contents:

  1. Firefox Add-on RESTclient – How to input POST parameters?
  2. What REST PUT/POST/DELETE calls should return by a convention?
  3. Avoid duplicate POSTs with REST
  4. RESTful Authentication
  5. RESTful URL design for search
  6. How can I handle many-to-many relationships in a RESTful API?
  7. How to post JSON to PHP with curl
  8. What is the proper REST response code for a valid request but an empty data?
  9. How to version REST URIs
  10. HTTP response code for POST when resource already exists
  11. Security of REST authentication schemes
  12. How to make remote REST call inside Node.js? any CURL?
  13. Best practice for partial updates in a RESTful service
  14. Groovy built-in REST/HTTP client?
  15. Designing URI for current logged in user in REST applications
  16. Unable to upload zip file through karate framework
  17. API pagination best practices
  18. How to use cURL to send Cookies?
  19. Spring 4 RestController JSON: characteristics not acceptable according to the request “accept” headers
  20. Jersey with Struts2 [duplicate]
  21. REST API Authentication
  22. Should I use Singular or Plural name convention for REST resources?
  23. How to download excel (.xls) file from API in postman?
  24. Where can I find jenkins restful api reference? [closed]
  25. Is it correct to return 404 when a REST resource is not found?
  26. When is it appropriate to respond with a HTTP 412 error?
  27. Websocket vs REST when sending data to server
  28. ‘Best’ practice for restful POST response
  29. Why does my C# client, POSTing to my WCF REST service, return (400) Bad Request?
  30. REST API DESIGN – Getting a resource through REST with different parameters but same url pattern

Leave a Comment