About the Master Data API
Master Data is how an external system writes 52ViKING’s configuration: what can be sold, how it is classified, what it costs, and which promotions apply to it.
Entities
Plus currencies, sales groups, store groups, user categories, user profiles, and images.
Three things to know before you write
All writes are asynchronous
Every POST returns 202 Accepted with a reference in the Location
header. Schema validation is synchronous, so bad payloads fail immediately with
400. Distribution to stores is not. Poll the location for the result.
Chain scope and store scope are different operations
POST /…/chain/{chain} hands the data to the enterprise controller, which
distributes identical master data to every store (article data excepted).
POST /…/chain/{chain}/store/{store} writes store-specific data handled by
that store directly. If you are unsure which you need, ask your FiftyTwo
consultant before loading production data.
Schema field descriptions sometimes reference Bpar.fieldname. Bpar is the
store configuration utility FiftyTwo consultants manage together with your
organisation, so those fields are configured outside this API.
Duplicate object_id values within a single POST body are resolved by the
API’s own rules. Deduplicate before sending, so you control which record wins.