Get store settings

GET /v1/settings/store

Requires: settings.view

Response Schema

GetStoreSettingsResponse

automaticQueueMatchingrequired

boolean

When false, every background QueueRun event short-circuits inside `matchPrintersAndJobs` and the auto-matcher does not assign jobs. The queue page surfaces a "Match queue now" button that bypasses this gate by passing `manual: true` to the matcher. Defaults to true so existing stores keep their current behaviour.

createdAtrequired

string

format: date-time

currencyrequired

string

currencySymbolrequired

string

defaultFallbackFilamentSystemProfileIdrequired

number

defaultFallbackFilamentUserProfileIdrequired

string

defaultPrinterSystemProfileIdrequired

number

defaultPrinterUserProfileIdrequired

string

defaultProcessSystemProfileIdrequired

number

defaultProcessUserProfileIdrequired

string

experimentalFeaturesrequired

object

generalSettingsrequired

object

idrequired

string

processLowPriorityJobsrequired

boolean

repairSlicerProfileValuesrequired

boolean

When true (the default), the cloud slicer clamps out-of-range / sentinel numeric values in the target slicer's printer/process/filament profiles (and the 3MF's embedded config) into the range that exact slicer build accepts, reproducing the desktop GUI's silent value tolerance so headless slices don't abort with CLI_INVALID_VALUES_IN_3MF (-18). Turn off to hand the profiles to the CLI verbatim. See packages/builders/slicers config-param-repair.

slicerrequired

string

storeIdrequired

string

updatedAtrequired

string

format: date-time

Example Response

200 OK — application/json

{
  "id": "string",
  "storeId": "string",
  "createdAt": "2026-08-24T03:58:56.088Z",
  "updatedAt": "2026-08-24T03:58:56.088Z",
  "processLowPriorityJobs": true,
  "automaticQueueMatching": true,
  "repairSlicerProfileValues": true
}