GET read-restricted custom-content now returns a 404 in V2 API

Hi there!

Our team is currently in the midst of migrating our endpoints to Confluence Cloud V2 API and we’ve come across one potential issue we’d like to bring up.

In the to-be-deprecated V1 API, if a user attempts to GET read-restricted custom-content, the response would fittingly return a 403, as they do not have the necessary permissions to view/access it. However, the V2 API now responds with a 404 instead. This seems problematic as we are now not able to conveniently differentiate between a missing and a restricted piece of custom-content for our users.

Is this something that is expected to be patched, or is there a good reason for this change of behaviour that we are missing?

Thanks in advance!


Hi @SamirMusaev

Atlassian has said that they’re no longer monitoring this forum for REST API v.2 gaps and that you should file a bug to get the item added to the queue using the following procedure: RFC-19: Deprecation of Confluence Cloud REST API v1 Endpoints - #25 by AshishShirode

1 Like