Demand planning API forecast upload fails due to dimension mismatch between source and Intacct

SCM Blue Yonder Luminate
, , , , , , , ,
1

We’re uploading forecast data to the demand planning API from our export tool, but consistently getting 422 Unprocessable Entity errors. The API response mentions ‘invalid date format’ but our dates look correct to us. We’re using format MM/DD/YYYY which matches our regional settings. The forecast includes weekly buckets for the next 52 weeks with quantities per SKU. When we manually enter the same data through the Luminate UI, it works fine. Our export tool generates JSON with date strings like ‘06/15/2025’ for forecast periods. The API documentation mentions date formats but doesn’t provide specific examples. We’re on BY 2022.2 and need to automate our weekly forecast uploads. Has anyone dealt with date format requirements in the demand planning API? Is there a specific ISO format we should be using?

2

Thanks, that makes sense. Our export tool generates dates like this:

"forecastPeriods": [
  {"periodStart": "06/15/2025", "quantity": 1500},
  {"periodStart": "06/22/2025", "quantity": 1600}
]

I’ll update the export logic to use ISO 8601 format. Should we include time components (hours/minutes) or just the date part?

3

The Luminate APIs are very strict about date formats. They require ISO 8601 format (YYYY-MM-DD) for all date fields, regardless of your regional settings. Your MM/DD/YYYY format won’t work. Try converting to 2025-06-15 format instead.

4

Another common issue is timezone handling. If your export tool is generating dates in local time but not including timezone information, the API might interpret them differently than you expect. Always include explicit timezone in ISO 8601 format, or use UTC to avoid ambiguity. The UI works because it automatically converts your browser’s local time to UTC before submission.