The DELETE method now has two problems:

• It allows a full table DELETE without filters - an expensive operation(can take a long time on big tables) and it can occur by accident
• A DELETE with a big in query parameter(?col=in.(1,2,3,4,5,....)) can err because of URL size limitations.

We can have the same interface as the new Bulk UPDATE for DELETE and solve the above problems.

DELETE /projects

[
  {"id": 1},
  {"id": 2},
  {"id": 3}
]

This would involve having a body for a DELETE method, which seems fine since other well-known APIs do it. There was also a previous discussion in #2125 (comment).