Status 409
Consent to the consequences is required
consent_required
When it happens
The write would change other data of the store: consent_kind names the kind of consequence, consequences counts what will change, consent_token is the fingerprint of what was shown.
What to do
If the consequences are acceptable, repeat the request with consent[<consent_kind>]=<consent_token>, keeping consents already given. If they changed meanwhile, you get a new 409 with a new token. For a variant line inside a product write, give the consent by changing that variant (variant_id).
Can’t find the answer, or the error keeps coming back? Write to us and quote the X-Request-Id from the response so we can find the request. Contact us
Endpoints that return it
- delete
/categories/{category}Archive a catalog category - patch
/products/{product}Change a product card: fields, categories, external ID - delete
/products/{product}Archive a product with its variants - patch
/products/by-external-id/{external_id}Create or update a product with its variants by its external ID - put
/products/{product}/optionsReplace the product options and lay out its variants - patch
/variants/{variant}Update a product variant - delete
/variants/{variant}Archive a product variant - patch
/variants/by-external-id/{external_id}Create or update a variant by its external ID - patch
/modifier-groups/{group}Update a modifier group and its option set - delete
/modifier-groups/{group}Archive a modifier group - patch
/modifier-groups/by-external-id/{external_id}Create or update a modifier group by external ID - delete
/price-lists/{price_list}Delete a wholesale price list; its assignment to customers is removed with consent - post
/orders/{order}/cancelCancel an order - post
/supplier-bills/{supplier_bill}/postPost a supplier bill: it enters payables and the purchase ledger - delete
/purchase-orders/{purchase_order}Delete a draft purchase order
Response body
application/problem+json · ConflictProblem
typestringrequiredMachine type of the problem: a stable code to branch on, such as insufficient_scope. Every type has a page in the error catalog.
titlestringrequiredShort summary of the problem in the language of the request.
statusintegerrequiredHTTP status of the response.
detailstringExplanation of this occurrence in the language of the request.
currentobjectThe record as it is now, the fields the conflict is about: on_hand for stock_on_hand_changed, status for rejected order changes, status and order_id for a closed draft.
external_idstringFor external_id_in_use and external_id_archived — the taken external ID.
consent_kindstringFor consent_required — the kind of consequence to agree to.
consequencesmap of integerFor consent_required — what will change: kind of data → number of records.
- Minimum:
- 0
consent_tokenstringFor consent_required — fingerprint of the shown consequences. Repeat the request with consent[<consent_kind>]=<consent_token>.
variant_idintegerFor consent_required of a variant line in a product write — the variant: the consent is given by changing that variant (PATCH /v1/variants/{variant}).
limitintegerFor plan_limit_reached, address_book_full, bulk_operation_queue_full and webhook_endpoint_limit_reached — the limit.
- Minimum:
- 0
fieldstringFor customer_contact_in_use — the contact that belongs to another customer: phone or email.
- Values:
phoneemail
existing_customer_idintegerFor customer_contact_in_use — the customer the contact belongs to.
receivedintegerFor upload_offset_mismatch — bytes the upload has received: the offset to continue from.
- Minimum:
- 0
operation_statusstringFor bulk_operation_finished — the status the operation finished with.