Get a folder's access rules

GET

/content/management/v1/folders/{id}/access-rules

const url = 'https://api.ebitex.io/content/management/v1/folders/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/access-rules';
const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};

try {
  const response = await fetch(url, options);
  const data = await response.json();
  console.log(data);
} catch (error) {
  console.error(error);
}

curl --request GET \
  --url https://api.ebitex.io/content/management/v1/folders/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/access-rules \
  --header 'Authorization: Bearer <token>'

The access rules declared directly on this folder, as role and action pairs. Actions are view, edit, delete and publish.

Rules cascade down the tree per action, and the nearest folder that declares any rule for an action decides it: only the roles listed there may take that action. A folder with no rules for an action inherits its parent’s, and an action no folder restricts is open to every role. This returns only what is declared here, not what is inherited.

Needs the key’s role to hold content.access.manage.

Key: a management key with content.management.read.

Authorizations

apiKey

Parameters

Path Parameters

required

string format: uuid

Responses

200

[ { "roleDefinitionId": "…", "action": "edit" } ]

401

missing_api_key or invalid_api_key: no key was sent, or it is unknown, revoked or expired.

402

payment_required: the organization’s subscription needs attention.

403

permission_denied: the key’s role lacks content.access.manage.

scope_denied: the key lacks this route’s scope. tier_required: the Content Management API needs the Pro plan or above. ip_denied: the caller’s address is outside the key’s allowed ranges. app_not_available: Content is not enabled for the organization.

404

No folder has this id.

429

Rate limit or quota exceeded; Retry-After says how long to wait. too_many_failed_authentications: too many bad keys from this address.