If you really want the nested route then that's fine but then you probably want something like [this](http://goo.gl/krlpjw) where you would have both routes. Really though we haven't been adding nested routes in the API for member actions (we've been leaving them until later) unless there is a good reason (e.g. id is not unique across the app). I think there are a few nested routes though that predate this decision.