Clone a namespace with all its data.
What gets cloned:
Use Cases:
For config-only copy (no data), use templates instead:
Documentation Index
Fetch the complete documentation index at: https://docs.mixpeek.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
REQUIRED: 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_API_KEY"
"Bearer YOUR_STRIPE_API_KEY"
Source namespace ID or name to clone from
Request to clone a namespace with all its data.
Clone creates a full copy of a namespace including:
Use Cases:
For config-only copy (no data), use templates instead:
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"
Successful Response
Response after initiating namespace clone.
Cloned namespace with new namespace_id
Source namespace that was cloned
Clone status: 'cloning', 'ready', or 'failed'
Celery 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 Celery task hydrates the rest of the data. None if source namespace has no retrievers.