Skip to content

List what points at a node

GET
/content/management/v1/experience/nodes/{id}/usages
curl --request GET \
--url https://api.ebitex.io/content/management/v1/experience/nodes/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/usages \
--header 'Authorization: Bearer <token>'

Lists what targets this node: redirect nodes, and components or nodes whose link fields point at it. Each of these blocks the node’s deletion.

Each item is { nodeId, name, path }. For a component, nodeId holds the component’s id and path is null. For which field each reference sits in, and where the node is published, use GET /experience/nodes/{id}/usages/closure.

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

id
required
string format: uuid

OK

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.

access_denied: the key’s role may not view this node.

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, or the key’s role cannot see it.

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