Skip to content

Delete a node

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

Deletes a node, together with the access rules and Template restriction set on it. A site root is deleted the same way.

Deletion is refused while anything still depends on the node: children (delete or move them first), a redirect or a link field pointing at it (see GET /experience/nodes/{id}/usages), or a live published version in any delivery environment (unpublish it first). The key acts as its role, so branch access rules apply: a node the role cannot view answers 404, and one it can view but not change answers 403 access_denied.

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

id
required
string format: uuid

No Content.

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 delete 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.

not_empty: the node has children. has_dependents: redirects or link fields target it; redirected_from lists them. node_published: the node is live in the delivery environments deliveryEnvironments names; unpublish it there first.

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