Replace a node's access rules
const url = 'https://api.ebitex.io/content/management/v1/experience/nodes/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/access-rules';const options = { method: 'PUT', headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'}, body: '{"rules":[{"roleDefinitionId":"2489E9AD-2EE2-8E00-8EC9-32D5F69181C0","action":"example"}]}'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request PUT \ --url https://api.ebitex.io/content/management/v1/experience/nodes/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/access-rules \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "rules": [ { "roleDefinitionId": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "action": "example" } ] }'Replaces every rule set directly on this node with rules, a list of { roleDefinitionId, action }. edit, delete and publish each imply view, which is added for you. An empty list removes the node’s own rules, so it inherits again.
Rules also govern the key itself, since it acts as a role: removing its role’s edit here stops the key editing this branch. The key’s role needs the content.access.manage permission.
Key: a management key with content.management.authoring.
Authorizations
Section titled “Authorizations”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters”Request Bodyrequired
Section titled “Request Bodyrequired”object
object
Examplegenerated
{ "rules": [ { "roleDefinitionId": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "action": "example" } ]}Responses
Section titled “ Responses ”The rules now set on the node, including any implied view rules.
validation_failed: an action other than view, edit, delete or publish.
missing_api_key or invalid_api_key: no key was sent, or it is unknown, revoked or expired.
payment_required: the organization’s subscription needs attention.
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.
No node has this id.
Rate limit or quota exceeded; Retry-After says how long to wait. too_many_failed_authentications: too many bad keys from this address.