Get Map Policy Brand View
Return full merged MAP policy view for a brand.
Match computation (matched/catalog_only/map_only, overrides, ignores,
changes) always runs over the FULL brand product set; skip/limit
only page the serialized products list. The response’s page
dict reports total — the full post-filter product count — so the
client can render pagination controls.
WHY limit is allowed all the way up to MAP_VIEW_MAX_PRODUCTS:
this view is a client-ASSEMBLED dataset. The MAP Policy page needs
every product at once (it filters/sorts/paginates client-side), so it
loops pages until it has them all — and because every page re-runs the
whole-brand match computation and then throws away all but its own
slice, an N-page brand used to cost N FULL recomputations (measured on
qa: a 2-page brand took ~7s, ~2x a 1-page brand). Letting one request
span the whole brand collapses that multiplier to a single
computation. The ceiling tracks the service constant rather than a
literal because the service caps the underlying product fetch at
MAP_VIEW_MAX_PRODUCTS regardless: a larger limit could never
return more products, only mislead. The DEFAULT stays 500 so existing
API/SDK consumers are unaffected.
Path Parameters
Query Parameters
Search filter for product name or key
Products to skip in the returned page
x >= 0Max products to return per page (capped at the service's whole-brand computation ceiling)
1 <= x <= 2000Cookies
Response
Successful Response