Is it possible to design an API like this?

Question

API

I am making a simple book reading service on Spring Boot.
I threw the following API structure: api/users/{id}/shelves/{id}/books/{id}/pages
It turns out the following order of obtaining data:

1. First, we get a list of users:api/users
   
2. Then we get a list of user shelves:api/users/{id}/shelves
   
3. The following is a list of books on the shelf:api/users/{id}/shelves/{id}/books
   
4. Then we get a list of pages of the book:api/users/{id}/shelves/{id}/books/{id}/pages
   
5. Next, we work with the pages of the book.
   

Wouldn't it be a mistake to simplify the structure to:

1. Get a list of users:api/users
   
2. Get a list of shelves for a specific user:api/users/{id}/shelves
   
3. Get a list of books on a specific shelf:api/shelves/{id}/books
   
4. Get a list of book pages:api/books/{id}/pages
   
5. Next, we work with the pages of the book.
   

Or is such a simplification not according to Feng Shui?

And another nuance: there are no particular difficulties with adding / viewing / updating / deleting information about books and shelves.
What if the book needs to be moved from one shelf to another?

Answer 1

If the book id is unique throughout the database, then api/books/{id}/pages is sufficient.

What if the book needs to be moved from one shelf to another?

Change an entry in the shelves_books link table. PATCH /api/books/{id} request with body { "shelf": shelfId }.