Retrieve a product question
One question in any state, with its answers. This is how you read a question’s status back: call it after approve or reject to confirm which state the write actually landed in, which matters most before a reject, since the same call declines a pending question and takes down a published one. THE SAME SHAPE THE LIST SERVES, and the same shape approve and reject answer with, so a row taken off a page can be re-read on its own rather than by walking the collection again. A 404 IS DELIBERATELY GENERIC and covers three conditions at once: no such id, an id belonging to another store, and a malformed id. Separating them would turn this route into a probe for which question ids exist in a store you cannot read.
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.
Path Parameters
Response
Success
