Most content management systems I have seen provide a technical backend UI to manage resources (as well as their meta data), and a user-friendly frontend to display nicely formatted web pages. So the views of a content admin and a frontend user on the same resources are very different in such a CMS. Here option 3 (individual APIs) seems to be most adequate *if you want to design your system similar to  such a CMS*. 

However, I guess there are also systems which behave more along the WYSIWYG philosophy and try to keep the admin's view very similar to a frontend user's view. That could make sense when the active/inactive flag is the only difference between the resource views, and no other meta data has to be maintained by an admin. If you want your system to be designed that way, option 1 seems to be more adequate, since it will make it a lot easier to develop a single UI which can be used by users and admins as well.

So ask yourself:

- How different **do you want** those use cases to be, and how different do you need the views on the data to be in these two use cases? 

The UI and use cases are where the requirements for you API are coming from - so that's where **your** requirements analysis has to start, and where your design decision should be based on. There is no braindead rule what the *"correct way to deal with it in a RESTFul API"* is.