# Delete multiple resources using filtered collection

**URL:** <https://discuss.jsonapi.org/t/delete-multiple-resources-using-filtered-collection/917>\
**Category:** Uncategorized\
**Created:** [March 2, 2017, 9:37pm UTC](https://discuss.jsonapi.org/t/delete-multiple-resources-using-filtered-collection/917 "2017-03-02T21:37:15Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![michaelhibay](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.jsonapi.org/michaelhibay/32/405_2.png) [@michaelhibay](https://discuss.jsonapi.org/u/michaelhibay)\
**Post date:** [April 19, 2017, 8:42pm UTC](https://discuss.jsonapi.org/t/delete-multiple-resources-using-filtered-collection/917/4 "2017-04-19T20:42:04Z")

</div>

I just went through a post in [here](http://discuss.jsonapi.org/t/alternative-ways-to-update-multiple-objects/952) which discusses the concept of a bulk transaction.

Upon further thought and time to contemplate, I think a specification filter strategy for this type of destructive action is probably ill advised. My initial thoughts were to say no, but I was able to see how this would be beneficial, but considering zachaysan’s comments regarding the failure states I can’t get behind this as a specification.

I think the appropriate way to accomplish this is a transaction resource which can take 1 or more operations, which contain 0 or more payloads and can fail or succeed on their own or as a transaction.

---

_[View the full topic](https://discuss.jsonapi.org/t/delete-multiple-resources-using-filtered-collection/917)._