@daviddavis, In this particular case, it was added based on feedback from @ehelms to be consistent across the APIs. That said, we can add a secondary route for this one as the filter :id can uniquely identify a filter.

Later when you get to the routes for filter rules, this is no longer going to hold true as there are multiple rule types being handled by the controller.  In those cases, it will be the combination of filter id + rule id that will represent a unique entity (rule).