You can certainly do two routes but have a centralized method on a single controller. If you have it nested under the subscriptions route I don't know that I see a need to have it on just the organization. Considering that the other manifest functions (delete, refresh, import) are all under `../subscriptions/` the manifest history should as well to me.