Thanks, @KaiMunechika for your time and the information provided.
I would love to reach out to you and therefore created a more specific question here:
Yes, we will have whiteboard-specific endpoints, that will be separate from page ones, and part of the v2 API.
What would be the advantage of splitting the endpoints instead of using query parameters?
We would need this for our App we currently use the v1 endpoint described in my post above.
Will there be an endpoint to show the tree of how the content (whiteboards, pages are related to each other in a space like ancestors/children?
Thanks in advance!