@AlexWilliams We have a similar use case in several of our apps. Did you consider adding something like a /page/{id}/ancestors endpoint so we can at least get all of those in one call?
Another minor thing is that v2 APIs require us know before the call of what type a certain content is, because there is no generic /content endpoint anymore. This also involves extra calls because we need to guess: 1. page, 2. blogpost, 3. custom, etc.