Find nodes by category

GET

/content/management/v1/experience/nodes/category-filter

const url = 'https://api.ebitex.io/content/management/v1/experience/nodes/category-filter?categoryId=2489E9AD-2EE2-8E00-8EC9-32D5F69181C0';
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/experience/nodes/category-filter?categoryId=2489E9AD-2EE2-8E00-8EC9-32D5F69181C0' \
  --header 'Authorization: Bearer <token>'

Finds the nodes classified under a category, given as categoryId. Sub-categories count, and so does a category chosen in a category field of the node’s payload, as well as a category the node is tagged with.

matchingNodeIds are the matches the key’s role can view. ancestorNodeIds are the ancestors of those matches, so a tree loaded one level at a time can be expanded down to each of them.

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

Authorizations

apiKey

Parameters

Query Parameters

categoryId

required

string format: uuid

Responses

200

{ "matchingNodeIds": ["…"], "ancestorNodeIds": ["…"] }

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

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.

429

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