mutation SaveShopTransferParameters($request: SaveShopTransferParametersCommandRequestInput!) {
SaveShopTransferParameters(request: $request)
}{
"request": {
"salesChannelId": "string",
"maxFilesPerArchive": 1,
"quickSyncArticleCount": 1,
"maxImagesPerArchive": 1,
"orderTransferCount": 1,
"maxArchiveSizeInKilobytes": 1,
"maxImageArchiveSizeInKilobytes": 1
}
}{
"data": {
"SaveShopTransferParameters": true
}
}SaveShopTransferParameters
Saves the six transfer parameters that control archive/quick-sync/order transfer thresholds toward the JTL-Shop (legacy ParameterValidationService/ParameterDefaults). Note on scope: although this route is addressed by a shop’s sales channel id, the six values below are NOT scoped to that shop. They are persisted globally in dbo.tOptions and apply to every JTL-Shop instance the tenant operates, because the legacy JTL-Shop connector itself only ever reads a single, global set of these settings. The salesChannelId in the route exists solely so the request can be rejected with 404 when it does not name an existing Wawi-managed webshop; once that check passes, the write always targets the same global rows regardless of which valid salesChannelId was used to reach this route. A caller that saves these parameters via shop A and then reads them back via shop B sees the exact same values - that is the intended legacy behavior, not a bug of this endpoint.
SaveShopTransferParameters(request: SaveShopTransferParametersCommandRequestInput!): Boolean!Arguments
Returns
mutation SaveShopTransferParameters($request: SaveShopTransferParametersCommandRequestInput!) {
SaveShopTransferParameters(request: $request)
}{
"request": {
"salesChannelId": "string",
"maxFilesPerArchive": 1,
"quickSyncArticleCount": 1,
"maxImagesPerArchive": 1,
"orderTransferCount": 1,
"maxArchiveSizeInKilobytes": 1,
"maxImageArchiveSizeInKilobytes": 1
}
}{
"data": {
"SaveShopTransferParameters": true
}
}Was this page helpful?