Expose the api SOMEHOW so you can manage stuff

[randomouscrap98]

So, contentapi has an awesome management system builtin, but you can't access it. That alone could give you access to so much junk, such as the admin logs and content restoration and the whole dang thing. But it's difficult to expose it because it's not like it's restricted. Perhaps there could be a setting in contentapi that only allows super users to access the endpoint, and then you just expose it as normal through nginx? Another option is to hide it behind header authentication like .htaccess or whatever the equivalent is in nginx.

[randomouscrap98]

problem with building it into contentapi: how will it know you're logged in? you'd have to manually pass the token somehow and that's annoying.