Publish a product question
Authorizations
A secret API key. Publishable keys cannot reach this API. A key may carry an expiry, and an expired key is refused exactly like an unknown one, with a 401 that names no reason; check the key's expires_at in the dashboard rather than inferring it from a response. When a merchant rolls a key's secret they choose a grace window of up to 3 days, and for its duration BOTH the new secret and the one it replaced authenticate, so an integration moves over on its own deploy schedule instead of at the instant the button is pressed. Move before the window closes: after it, the old secret is refused. Nothing else about this contract moves with a roll. The key keeps its id and its scopes, so the only thing an integration updates is the credential itself.
Headers
A unique key per logical write. Replaying a request with the same key returns the first response byte for byte instead of applying the write twice.
Path Parameters
Body
Takes no parameters, and an empty body is expected. Publishes an existing shopper-authored question so it appears beside the product, with its answers, for every shopper. The status it writes is "published"; the route is named for the act and the resource is named for the state, so do not send ?status=approved to the list expecting to find it. Idempotent by construction: the status is an absolute assignment from any current state, so a replay outside the idempotency window converges on the same row. Reversed by POST /product-questions/{questionId}/reject. The response is the SAME shape the read serves, so you can treat it as a fresh read rather than following it with a GET. THE BODY REFUSES status, body, answers and every provenance key (id, store_id, customer_id, created_by, created_at, updated_at) BY NAME with a reason. status is refused because a field cannot say whether you meant to decline a pending question or take down a live one, which is exactly why there are two routes.
Response
Success
