Skip to main content
POST
Clone Taxonomy

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

taxonomy_identifier
string
required

Source taxonomy ID or name to clone.

Body

application/json

Request to clone a taxonomy with optional modifications.

Purpose: Cloning creates a NEW taxonomy (with new ID) based on an existing one, allowing you to make changes that aren't allowed via PATCH (config, retriever_id, collections). This is the recommended way to iterate on taxonomy designs.

Clone vs Template vs Version:

  • Clone: Copy THIS taxonomy and modify it (for iteration/fixes)
  • Template: Create taxonomy from a reusable pattern (for new projects)
  • Version: (Not implemented) - Use clone instead

Use Cases:

  • Fix configuration errors without losing join history
  • Change retriever or input mappings
  • Change target collections
  • Test modifications before replacing production taxonomy
  • Create variants for different datasets

All fields are OPTIONAL:

  • Omit a field to keep the original value
  • Provide a field to override the original value
  • taxonomy_name is REQUIRED (clones must have unique names)
taxonomy_name
string
required

REQUIRED. Name for the cloned taxonomy. Must be unique and different from the source taxonomy.

Minimum string length: 1
Examples:

"product_tags_v2"

"org_hierarchy_strict"

description
string | null

OPTIONAL. Description override. If omitted, copies from source taxonomy.

Example:

"Cloned from product_tags with updated retriever"

config
FlatTaxonomyConfig · object

Configuration for a flat taxonomy - single source collection with one retriever.

Example:

Response

Successful Response

Response after cloning a taxonomy.

taxonomy
TaxonomyModel · object
required

Cloned taxonomy configuration with new taxonomy_id.

Examples:
source_taxonomy_id
string
required

ID of the source taxonomy that was cloned.