Skip to content

Rename a category group

PUT
/content/management/v1/taxonomy/groups/{id}
curl --request PUT \
--url https://api.ebitex.io/content/management/v1/taxonomy/groups/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0 \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{ "name": "example", "rowVersion": 1 }'

Changes the group’s display name, the only property this route changes. The external id, and so every category path, stays the same.

Send the rowVersion you last read to be told when someone else has renamed the group since. Omit it and the last write wins.

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

id
required
string format: uuid
Media typeapplication/json
object
name
required
string
rowVersion
null | integer | string format: uint32
/^-?(?:0|[1-9]\d*)$/
Examplegenerated
{
"name": "example",
"rowVersion": 1
}

The updated group, shaped as in the list.

validation_failed: name is missing or blank.

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.

permission_denied: the key’s role lacks content.taxonomy.manage.

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 group has this id in the key’s environment.

concurrency_conflict: the rowVersion sent is not the group’s current one, so someone else has changed it; currentRowVersion is what it is now. taxonomy_read_only: the group or category comes from a content provider and changes only when that provider is refreshed. inherited_read_only: the item is inherited from another environment and can only be changed there; sourceEnvironmentId names it.

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