Skip to main content
Both settings live on a product and need the Growth plan (or higher) to turn on. Turning them off and reading them is never gated. A call that turns one on below Growth answers 403 with code: "FEATURE_LOCKED":

Post-purchase offer

{id} is the product buyers purchase first. Fields you leave out of a PUT keep their value.
A 400 carries a code saying what is wrong with the offered product: same_product, other_mode, pay_what_you_want, credits, not_available, checkout_disabled or too_cheap. When a buyer accepts, you receive order.completed for the new order (like any order) and order.post_purchase_accepted with parentOrder.id, the order it followed.

Social proof

The public read returns aggregates only (cached about 60 seconds), the same numbers the checkout shows:
Counts include live, non-refunded orders only. recent.place is a city when the payment recorded one, otherwise a two-letter country code. enabled is false (and every other field null) when the setting is off or your plan no longer includes it.