Bulk get content access data

post

https://api.seismic.com/cm/v1/contentAccessPermissions

Retrieve content access data in bulk for up to 1000 TeamSite/content targets in one call. Each result returns the requested TeamSite/content pair together with every explicit member permission entry that currently applies.

Content Access Permissions

Content Access Permissions are enforced at the TeamSite root, folder, and file level and support these permission ids:
403 (Can view): View, comment, and approve content.
404 (Can edit): Edit and add folders, and edit, add, publish, or move files.
405 (Can manage): Edit, add, publish, move, delete, and manage content access.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Body Params

Array of TeamSite/content pairs to resolve. Each object identifies one target item. Use teamSiteId as either a TeamSite UUID or 1 for the default TeamSite. Use contentId as an item UUID or root for TeamSite home. Maximum 1000 request objects per call.

Request body samples

[
  {
    "teamSiteId": "1",
    "contentId": "root"
  },
  {
    "teamSiteId": "fa71f245-d1be-41c7-bb51-129ca60f9e46",
    "contentId": "be802102-e3b0-40b7-a790-3d50c4c21649"
  }
]

Array of TeamSite/content identifiers to resolve. Use root as contentId to return access configured on TeamSite home.

Responses

`403` in legacy environments.

`403`; clients should handle both `401` and `403` for auth-related failures.

Language

Credentials

Header

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

Request body samples

200Successfully resolved content access permissions for every requested TeamSite/content pair.

400Bad Request. The payload format is invalid, or the request exceeds operation constraints such as the maximum batch size.

401Unauthorized. The request is missing a valid authentication token or the token has expired. For backward compatibility, clients should also handle equivalent auth failures returned as 403 in legacy environments.

403Forbidden. The caller does not have sufficient permissions to read content access settings for one or more requested items. In some legacy environments, expired or missing authentication may also surface as 403; clients should handle both 401 and 403 for auth-related failures.

404Not Found. One or more provided TeamSite or content identifiers cannot be resolved.

500Internal Server Error. The service failed while resolving requested permission data.

`403` in legacy environments.

`403`; clients should handle both `401` and `403` for auth-related failures.