Reconfigure the namespace’s Qdrant collection to include vectors from all deployed plugins.
When to use this: After deploying a new plugin to a namespace that already has data (points_count > 0). The auto-rebuild (Phase 1) only works on empty collections. For namespaces with existing data, use this endpoint to rebuild the schema, then re-trigger batches to re-ingest.
WARNING: This is destructive!
Workflow:
POST /plugins/uploads/{id}/confirmPOST /plugins/{id}/deployPOST /plugins/reconfigure with {"confirm": true}collections_to_reprocessResponse includes:
vectors_added: New vector indexes added by the reconfigurevectors_total: All vector indexes in the reconfigured collectioncollections_to_reprocess: Collection IDs to re-trigger for data re-ingestionDocumentation 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"
Request to reconfigure a namespace's Qdrant collection schema.
This is a destructive operation: it deletes and recreates the Qdrant collection with merged vector definitions from all deployed plugins. Existing data is lost and must be re-ingested by triggering batches on each collection.
Must be True to confirm this destructive operation. Existing Qdrant data will be deleted and must be re-ingested.
Namespace reconfigured successfully
Response from reconfiguring a namespace's Qdrant collection.
The reconfigured namespace
Operation status: 'reconfigured' or 'no_changes_needed'
Number of Qdrant points that were in the collection before reconfigure
Names of new vector indexes added to the schema
All vector index names in the reconfigured collection
Collection IDs that need to be re-triggered to populate new vectors
Human-readable status message