Retrieve review settings
The store’s review policy, and the context every other read in this family is missing. All of them serve approved reviews only, and what “approved” MEANS is set here: a store with auto_publish on publishes whatever a shopper writes, one with eligibility_mode purchase_gated publishes only verified buyers, and one with require_moderation on holds everything for a human. Read this before deciding how much weight to give a rating. syndicate_group_reviews IS THE FIELD THAT CHANGES HOW YOU READ THE REST. With it on, a review written on one product also appears on its group siblings and the rating is pooled across the group, so summing per-product counts double counts and one moderation call moves several products’ visible ratings at once. A STORE THAT HAS NEVER SAVED SETTINGS ANSWERS 200 WITH THE DEFAULTS, not 404. The policy is in force either way, so a 404 would claim the store has no review policy when an unconfigured store moderates and does not auto-publish. updated_at is null there, and that is how you tell a saved policy from the fallback: there is no row, so there is no timestamp, and a zero date or a fresh now() would each state a fact the server does not have. blocked_phrases IS NOT PUBLISHED AND WILL NOT BE. It is the merchant’s own moderation-evasion word list, so handing it over would hand over the enforcement boundary itself: anyone holding it knows precisely which wordings pass. If a future need is only “is screening configured”, the additive field is a count, not the list. allow_media and allow_video let you distinguish “the merchant turned attachments off” from “nobody has uploaded any”, which are different facts behind the same empty media array on a review. READ ONLY. Nothing on this API writes review settings, because auto_publish and require_moderation ARE the moderation policy: a key able to set them could turn moderation off and then publish anything through the ordinary shopper submit path. write_reviews buys clearing a queue, never redefining what the queue is for.
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.
Response
Success