Thank you for your feedback! We are looking for any blockers for V1 → V2 migration, and these are great examples.
Hopefully the below provides some additional clarify & reassurance:
- Space Icon → although this has not yet been documented / “officially supported” just yet, if you pass the query param
include-icon=trueto the V2 spaces endpoint, you should get back the space icon link - Space Metadata
- In terms of labels, hopefully this answers your question (you can rest assure we are aware and working to close this gap)
- Is there any other metadata you rely on?
- Space Permissions → similar to the above, we are hoping to release a dedicated space permissions endpoint soon. You can test it out right now in your browser:
v2/spaces/id-here/permissions - Author profile picture & name → Using accountId field, profile picture and name can be retrieved using V1 Get user endpoint
- Page history / version object not complete → For V2 endpoints, we moved towards just having the
versionsendpoints andversion detailsendpoints. Given this & the above V1 user endpoint for additional information about the user, is there any field that you are not able to retrieve that would be a blocker for you? - View format → this in the works and will be released as soon as we are able!
- Ability to fetch multiple formats in one request → currently this is not supported, if there is enough of an ask from vendors to support this then we will be able to prioritize this work!