Clone Namespace
Clone a namespace with all its data.
What gets cloned:
- Namespace configuration (extractors, payload indexes)
- Buckets (metadata, references same S3 files)
- Collections (full copy of all vectors/embeddings)
- Retrievers (pipeline configuration)
Use Cases:
- Create staging environment from production
- Backup namespace with all data
- Fork namespace for experimentation
For config-only copy (no data), use templates instead:
- POST /templates/namespaces/from-namespace/
- POST /templates/namespaces//instantiate
Headers
Bearer token authentication using your API key. Format: 'Bearer sk_xxxxxxxxxxxxx'. You can create API keys in the Mixpeek dashboard under Organization Settings.
"Bearer YOUR_MIXPEEK_API_KEY"
Path Parameters
Source namespace ID or name to clone from
Body
Request to clone a namespace with all its data.
Clone creates a full copy of a namespace including:
- Namespace configuration (extractors, indexes)
- Buckets (metadata, references same S3 files)
- Collections (full copy of all vectors/embeddings)
- Retrievers (pipeline configuration)
Use Cases:
- Create staging environment from production
- Backup namespace with all data
- Fork namespace for experimentation
For config-only copy (no data), use templates instead:
- POST /templates/namespaces/from-namespace/{id}
- POST /templates/namespaces/{template_id}/instantiate
Name for the cloned namespace (must be unique)
1"production_staging"
"backup_2024_01"
Which resources to include. Defaults to collections + retrievers.
Override description. If omitted, copies from source.
"Staging clone from production"
Source org ID for cross-org cloning (admin only).
"org_abc123"
Response
Successful Response
Response after initiating namespace clone.
Cloned namespace with new namespace_id
Source namespace that was cloned
Clone status: 'cloning', 'ready', or 'failed'
Task ID for tracking clone progress
Summary of cloned resources (present when ready)
Pre-allocated retriever ID for the primary cloned retriever. Present immediately so callers can navigate to the retriever detail page while the background task hydrates the rest of the data. None if source namespace has no retrievers.

