Sign inConnect your agent
notableaddedAtlassian calls it: Added

New V2 Confluence Permissions REST APIs

Announced
Tags
rest-confluence-cloud
Endpoints
GET /wiki/api/v2/{content-type}/{id}/restriction-state PUT /wiki/api/v2/{content-type}/{id}/restriction-state GET /wiki/api/v2/{content-type}/{id}/permissions POST /wiki/api/v2/{content-type}/{id}/permissions PUT /wiki/api/v2/{content-type}/{id}/permissions DELETE /wiki/api/v2/{content-type}/{id}/permissions
Severity
notable, set by reef/atlassian-rule-v2
Source
https://developer.atlassian.com/changelog/#CHANGE-3521

What's changing We are introducing new Confluence Cloud REST API v2 endpoints to manage content permissions and restriction states. These endpoints provide a consistent way to handle permissions across multiple content types, including pages, blog posts, databases, whiteboards, and folders.

The new endpoints are:

  • GET /wiki/api/v2/{content-type}/{id}/restriction-state: Retrieves the current restriction state of the content.
  • PUT /wiki/api/v2/{content-type}/{id}/restriction-state: Updates the restriction state (for example, to make content restricted or open).
  • GET /wiki/api/v2/{content-type}/{id}/permissions: Lists the specific permissions (read and update) applied to the content.
  • POST /wiki/api/v2/{content-type}/{id}/permissions: Adds new permissions for a user or group.
  • PUT /wiki/api/v2/{content-type}/{id}/permissions: Updates existing permissions.
  • DELETE /wiki/api/v2/{content-type}/{id}/permissions: Removes permissions.

What you need to do If you are building new integrations or migrating from the V1 content restrictions API, we recommend using these new v2 endpoints.

The text above is the source's. reef added the severity, the dates it could read from the text, and the endpoints and scopes named in code.