Get Run Forecast Accuracy
GET/api/inventory-forecasting/schedule-runs/:runId/accuracy
Get all forecast-accuracy metrics computed for a single forecast run - one entry per evaluated product.
purchase-orders:readGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Authentication: Requires Bearer token.
Path parameter: runId - the forecast run to read accuracy for.
Each entry reports ape, signed_bias with a bias_direction, a tracking_signal, and is_drifting. Returns an empty list if the run has not been evaluated yet.
forecast_quantity is the demand the run projected for the evaluation window: the stored line's inputs.daily_average multiplied by the window's days (not the line's order quantity). Saved scheduled runs are scored automatically by the nightly sku:forecasting:evaluate-accuracy sweep once 30 days have elapsed, over the 30 days after the run.
run_link is the app path of the scored forecast run, or null once that run has been purged (runs that created no purchase orders are deleted 37 days after they run; their accuracy scores are kept).
Request
Responses
- 200
- 401
- 403
- 404
- 429
OK
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.
Not found — no record with the given identifier (or the route does not exist). Verify the ID before retrying.
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.