Hello im about to create dasbord for my website..
Dashboard will have multiple subpages like users, posts, roles etc..
I was thinking i would use only one rest api endpoint for those resources like
/admin/{users}
/admin/{projects}
/admin/{roles}
and create enum for each of those which will be used later on to query data.
Is this good practice, or i should create rest api endpoint for each of those
Those links are more pages under the admin area of your website.
An api call would typically go to: /api/users, /api/projects, etc.
An HttpGet to /api/users would return all the users in application as a collection of DTOs; usually as JSON.
To return a specific user with id=4. HttpGet to /api/users/4.
There are lots of resources online; the above is a very basic example
If your API is follows the original REST specification then what URLs you use makes no difference. In fact it is better if they are unpredictable. That way people don't hard code them into clients. You should use a media type like Hypertext Application Language which will allow hypermedia traversal of your endpoints using rels. This decouples the client from the server and lets you change your URLs in future if you need to without breaking the client.
To save you pain let me just disclose that pretty much noone follows the original REST specification so while this is the best way to do it you won't find much help online if you go for proper REST.
