Upload Property Overrides Csv
Upload per-ProductType OR per-Category enrichment overrides from CSV.
Required columns: product_type_key, property_key. Optional columns: prompt_name_override, ai_matching_guidance_override, enrichment_config_override_json.
Target syntax in product_type_key:
<key>→ per-ProductType override (writes onto the ProductType’s PropertyReference). Existing behavior, unchanged.category:<key>→ per-Category override (writes to thecategory_enrichment_overridescollection). Resolves at enrichment time when the ProductType hascategory=<key>set.
The category form lets a customer hold one prompt per category (e.g. Footwear / Apparel / Accessories) instead of duplicating the same override across every ProductType in that category.
Behavior:
- Idempotent upsert: each row replaces any existing override at the same target.
- Empty cells clear the corresponding field.
- Rows whose ProductType or Property don’t exist are recorded as skipped, not failed.
- Requires
product_type:write(covers both targets).
Cookies
Body
Request model for CSV upload.
CSV content as string
Response
Successful Response
Response model for batch CSV upload operations.
Number of new records created
Number of rows that failed
Total rows processed
Number of existing records updated
Number of existing null values cleaned up from the database
List of errors
Number of rows skipped due to null/empty values