Resolve a category path or id

GET

/content/management/v1/taxonomy/resolve

const url = 'https://api.ebitex.io/content/management/v1/taxonomy/resolve';
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/taxonomy/resolve \
  --header 'Authorization: Bearer <token>'

Looks a category up by path (such as topic/news/local) or by id, and returns it with its current path. Use it to turn a path you hold into the id every other route takes, or to show an id as a path. When both are sent, id wins. A path naming only a group never resolves.

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

Authorizations

apiKey

Parameters

Query Parameters

path

string

string format: uuid

Responses

200

{ "category": { … }, "path": "topic/news/local" }, with category shaped as in the group’s category list.

400

validation_failed: neither path nor id was sent.

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.

404

No category matches the path or id.

429

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