Accept or reject a single enrichment proposal.
Documentation Index
Fetch the complete documentation index at: https://docs.closient.com/llms.txt
Use this file to discover all available pages before exploring further.
Unique identifier of the enrichment proposal.
Request body for accepting or rejecting an enrichment proposal.
Reviewer's decision on the pending proposal. ACCEPTED queues the proposed value to be applied by the /captures/{id}/apply endpoint; REJECTED discards it. Only ACCEPTED and REJECTED are valid here — PENDING (the initial state) cannot be set via this endpoint.
ACCEPTED, REJECTED OK
AI-generated enrichment proposal for a product field.
Unique proposal identifier (UUID).
Product field targeted by this proposal. One of: name, description, brand_name, category, ingredients, ai_summary, images.
50Current value of the field on the linked product (may be empty).
AI-suggested replacement value for the field.
Model confidence score from 0.00 to 1.00 (two decimal places).
^(?!^[-+.]*$)[+-]?0*\d*\.?\d*$Free-form explanation of why this change was proposed.
Identifier of the system that generated this proposal — for example bedrock_claude (vision extraction), hunter_io / apollo_io (contact discovery), local_database (GTIN lookup). Free-form string; not enumerated on the model.
100Review state of the proposal. Newly-generated proposals start PENDING; the review endpoint transitions them to ACCEPTED or REJECTED. Only ACCEPTED proposals are applied to the linked product by the apply endpoint.
PENDING, ACCEPTED, REJECTED Timestamp when the proposal was generated.
Developer-attached key/value data attached to this object. Up to 50 keys; key max 40 chars, value max 500 chars.
Timestamp when the proposal was reviewed.