GET/v1/tenants/{tenantId}/demand_planning/limits
Published upload limits Experimental
Use these values to size batches instead of hard-coding them.
Parameters
tenantIdrequired
Responses
application/jsonPublished limits for demand planning batch uploads. Requests above a hard limit are rejected with 413.
maxBodyBytesrequiredMaximum request body size in bytes as sent over the wire
- Format: int64
Example10485760maxCompressionRatiorequiredMaximum ratio between decompressed and compressed body size
- Format: int32
Example100maxDecimalsrequiredMaximum decimals in quantities and replenishment parameters
- Format: int32
Example4maxDecompressedBodyBytesrequiredMaximum request body size in bytes after gzip decompression
- Format: int64
Example52428800maxHorizonDaysrequiredMaximum number of days in a sales forecast horizon: two full years, the current one and the next
- Format: int32
Example731maxInlineRejectedItemsrequiredMaximum number of rejected items listed in a batch status
- Format: int32
Example500maxInlineValidationErrorsrequiredMaximum number of validation errors listed in a 400 response
- Format: int32
Example100maxItemsPerBatchrequiredMaximum number of items per batch
- Format: int32
Example20000recommendedBodyBytesrequiredRecommended request body size in bytes as sent over the wire, assuming gzip. A 1,000-item forecast batch of 731-day horizons is ~5.7 MB uncompressed and ~1.3 MB gzipped.
- Format: int64
Example1048576recommendedHorizonDaysrequiredRecommended number of days in a sales forecast horizon: to the end of next year
- Format: int32
Example731recommendedItemsPerBatchrequiredRecommended number of items per batch, sized for horizons of up to two years
- Format: int32
Example1000