Clear a node's payload

DELETE

/content/management/v1/experience/nodes/{id}/payload

const url = 'https://api.ebitex.io/content/management/v1/experience/nodes/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/payload';
const options = {method: 'DELETE', 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 DELETE \
  --url https://api.ebitex.io/content/management/v1/experience/nodes/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/payload \
  --header 'Authorization: Bearer <token>'

Removes a node’s page or redirect, leaving an address with nothing to serve. Its children and their addresses are unaffected. Once published, the node’s own path no longer answers with a page.

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. A workflow can also lock the node against edits.

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

Authorizations

apiKey

Parameters

Path Parameters

required

string format: uuid

Responses

200

The node, in the shape GET /experience/nodes/{id} returns.

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

access_denied: the key’s role may not edit 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.

404

No node has this id, or the key’s role cannot see it.

422

workflow_state_not_editable: the node’s workflow state does not allow edits; state and definition name it.

429

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