Skip to main content
POST
Clone Collection

Authorizations

Authorization
string
header
required

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

Path Parameters

collection_identifier
string
required

Source collection ID or name to clone.

Body

application/json

Request to clone a collection with optional modifications.

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

Clone vs Template vs Version:

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

Use Cases:

  • Change feature extractor configuration without breaking production
  • Modify field_passthrough to include/exclude fields
  • Switch to different source (bucket or collection)
  • Test modifications before replacing production collection
  • Create variants (e.g., different embedding models)

All fields are OPTIONAL:

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

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

Minimum string length: 1
Examples:

"product_embeddings_v2"

"video_frames_clip_v2"

description
string | null

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

Example:

"Cloned from product_embeddings with CLIP v2"

source
SourceConfig · object | null

OPTIONAL. Override source configuration. If omitted, copies from source collection. Allows switching between buckets or collections.

Example:
feature_extractor
FeatureExtractorConfig · object | null

OPTIONAL. Override feature extractor configuration. If omitted, copies from source collection. This is where you'd change models, parameters, or field_passthrough.

Example:
enabled
boolean | null

OPTIONAL. Override enabled status. If omitted, copies from source collection.

metadata
Metadata · object | null

OPTIONAL. Override metadata. If omitted, copies from source collection.

taxonomy_applications
TaxonomyApplicationConfig · object[] | null

OPTIONAL. Override taxonomy applications. If omitted, copies from source collection.

Response

Successful Response

Response after cloning a collection.

collection
CollectionModel · object
required

Cloned collection configuration with new collection_id.

Examples:
source_collection_id
string
required

ID of the source collection that was cloned.