| While things often have parents and children, they also very frequently stand alone. Also, sometimes you don't want to leak private data (org id's) in public content (a blog post) What I recommend is follow the resource standards from something like jsonapi, and organize your routes like this: /organizations/:organization_id /organizations/:organization_id/blogs -> returns a list of links to blogs (maybe including the very most basic data, like blog title and byline) /blogs/:blog_id -> one blog, has a link to organization, for going "up" the hirearchy, but only returned for authenticated users (if that's necessary in your use case) /blogs/:blog_id/sections -> links to list of sections /blogs/:blog_id/threads -> links to list of threads /threads/:thred_id -> one thread, but links to parents as above /sections/:section_id -> same as threads you get the idea. I've done it this way and I feel like it ends up being very easy to wrap my head around where things are, and how they relate to one another. One of my favorite example APIs is stripe. the layout makes sense, routes make sense, and it's a very complex system which becomes easy to understand and the routes aren't insanity, if you are looking for a very public example |