Skip to content

Remove a category group from the environment

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

Stops the key’s environment using the group. The group and its categories stay in the organization’s vocabulary and in every other environment that uses them; only this environment’s use, and its metadata definition for the group, are removed. Nothing is changed on your behalf: it is refused while content here is classified with one of the group’s categories, or a category field here names the group.

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

id
required
string format: uuid

OK

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.

The key’s environment does not use this group.

group_in_use: something in this environment still uses the group; usages lists each usage as { sourceKind, sourceId, app, environmentId, environmentName, displayName }, gathered from every app that classifies with the vocabulary — app is content or assets, and environmentId/environmentName are set for a usage inside an environment. inherited_read_only: the item is owned by a realm above the key’s own and can only be changed there; ownerRealmId 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.