Some things we have struggled with so far when switching away from the deprecated endpoints:
- No way to get favourited spaces in v2 API
- v1 API: /wiki/rest/api/space?favourite=true
- No simple way of getting labels used in a space in v2 API
- v1 API: /wiki/rest/api/space/{spaceKey}/content?expand=metadata.labels
- In v2 API I would have to: Get pages & blogposts on a space → Then get labels separately for each page & blogpost, turning the one v1 API call in to huge amount of v2 API calls.
- Get pages from space method of REST API v2 missing depth parameter
- No way to get page authors in v2 API
- Confluence API v2: How to get page authors information? - #4 by SimonKliewer
- We use the logged in users permissions to make our requests against Atlassian APIs (ACT_AS_USER user impersonation), this ensures that we are not exposing data to users that don’t have the rights to view it. The suggested solution is to use our apps permissions to fetch this information instead of the users because the user might not have the rights to call the user search API. Wouldn’t that mean that we are circumventing Atlassian set permissions?