Isn't the core issue that some developers would like to have the magical solution that solves/answers all use cases? You don't design your APIs in a vacuum. Yo

Isn't the core issue that some developers would like to have the magical solution that solves/answers all use cases? You don't design your APIs in a vacuum. You have use cases. You should have basic ones still. You build your API v0 against those use cases, not against your data model or your architecture. Then you _monitor_ usage, you _consult/discuss_ with your users to see how to refine/augment your API to better serve their needs. REST or anything else matters little, as long as you do the job: listen and understand your user needs (it doesn't happen only once) and adapt.