Two Web APIs 2.2 with Identity 2.0 for one database

Hello. Can i create two Web APIs 2.2 with Identity 2.0 for one database? I want to create one Web API for some actions( to the public ), and another Web API for some other actions( administrators only ). Just for a security measure i want to separate them, so that the public doesn't even get to know about the existence of the second Web API. Both must use authentication, but for the same database. Would this strategy be a problem? How can i achieve this?

I also want to know which information does the Bearer Token contains... i read in an article that it contains infos of the fields in the user table, is that right? If it is, so whenever the client tries to access some method of the Web API, the ASP.Net Identity goes to the database or just analyse the Token at the application layer? Thanks