A valid request URL is required to generate request examplesnull{
"detail": "<string>"
}{
"detail": "<string>"
}{
"detail": "<string>"
}{
"detail": "<string>"
}{
"detail": "<string>"
}{
"detail": "<string>"
}Save the thresholds behind the computed product badges
Replaces the merchant’s badge thresholds (all six counts are required; new_in_date_source defaults to published_at). Side effects: a new settings version is stored with the caller as author, and every collection that syncs back to Shopify is re-ordered there with the new badges (best effort: a failed re-order is logged, the save still succeeds). Answers null.
A valid request URL is required to generate request examplesnull{
"detail": "<string>"
}{
"detail": "<string>"
}{
"detail": "<string>"
}{
"detail": "<string>"
}{
"detail": "<string>"
}{
"detail": "<string>"
}Authorizations
Shopify App Bridge session token of the embedded Depict: Search & Merchandising app. The shop in the token determines the merchant; merchant_id parameters must belong to that shop.
Query Parameters
Lite merchant id, e.g. shopify-<shop id>.
Body
A product is New in for this many days.
How many top sellers get Bestseller.
How many bottom sellers get Slow mover.
Low stock below this percentage of variants in stock.
Days of orders the sales-based badges are computed over.
How many products get Trending.
Defaults to published_at.
published_at, created_at Response
Saved.
Was this page helpful?