Test taxonomy configuration (validation only)
⚠️ VALIDATION ENDPOINT ONLY - Not for production enrichment!
This endpoint validates taxonomy configuration with 1-5 sample documents. Results are returned immediately and NOT persisted to any collection.
❌ DO NOT USE FOR:
- Enriching entire collections (use taxonomy_applications instead)
- Batch processing documents (automatic during ingestion)
- Persisting enriched documents (use retriever pipelines instead)
✅ USE THIS FOR:
- Testing taxonomy configuration is correct
- Validating retriever finds matching taxonomy nodes
- Checking enrichment fields are properly applied
- Development/debugging taxonomy setup
📚 FOR PRODUCTION ENRICHMENT:
Automatic (during ingestion):
- Create taxonomy: POST /taxonomies
- Attach to collection: PUT /collections/ with taxonomy_applications field
- Ingest documents: Documents are automatically enriched by engine
On-the-fly (during retrieval):
- Add taxonomy_join stage to retriever pipeline
- Execute retriever: GET /retrievers//execute
- Results include enriched documents (not persisted)
See API documentation for Collections and Retrievers for details.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Taxonomy ID or name to validate
Query Parameters
Optional taxonomy version (defaults to latest)
Body
- ExecuteTaxonomyRequest
- Payload
Request model for on-demand taxonomy validation and testing ONLY.
⚠️ IMPORTANT: This endpoint is ONLY for testing taxonomy configuration with sample documents.
DO NOT USE THIS FOR BATCH ENRICHMENT: ❌ Do NOT use this to enrich an entire collection ❌ Do NOT use source_collection_id expecting batch processing ❌ Do NOT use target_collection_id expecting persistence
HOW TAXONOMY ENRICHMENT ACTUALLY WORKS:
✅ Automatic during ingestion: Attach taxonomies to collections via taxonomy_applications
✅ On-the-fly in retrieval: Add taxonomy_join stage to retriever pipelines
This endpoint validates:
- Taxonomy configuration is correct
- Retriever can find matching taxonomy nodes
- Enrichment fields are properly applied
For production enrichment, see:
- Collections API: attach taxonomies via
taxonomy_applicationsfield - Retrievers API: add
taxonomy_joinstage for on-the-fly enrichment
Full taxonomy model with configuration (fetched from DB by controller)
Optional retriever configuration override for testing. If omitted, uses the retriever configured in the taxonomy.
Sample documents to test enrichment (typically 1-5 docs). Results are returned immediately, not persisted. ⚠️ Do NOT pass collection_id expecting batch processing!
⚠️ IGNORED IN ON_DEMAND MODE. This field exists for legacy compatibility only. To enrich collections, use taxonomy_applications on the collection.
⚠️ IGNORED IN ON_DEMAND MODE. This field exists for legacy compatibility only. Results are never persisted via this endpoint.
Must be 'on_demand'. BATCH mode is NOT supported via API. Batch enrichment is automatic (triggered by engine during ingestion).
on_demand, batch Batch size for the scroll iterator
1 <= x <= 10000Additional filters applied to the source collection prior to enrichment.

