Bulk Resolve Demand Anomalies
POST/api/inventory-forecasting/anomalies/bulk-resolve
Apply the same resolution decision to many demand anomalies at once - the fast path after Detect Demand Anomalies. Unknown IDs are skipped; the response reports how many were actually updated.
Authentication: Requires Bearer token.
Status meanings match Resolve Demand Anomaly: excluded (drop from baseline), smoothed (replace with expected value), kept_tagged (keep, optionally tagged to a promotion), detected (reset). Only excluded and smoothed points are removed/replaced when a build runs with exclude_detected_anomalies true.
Body fields:
- anomaly_ids (required): array of anomaly IDs, at least one.
- status (required): excluded, smoothed, kept_tagged, or detected.
- promo_window_id (optional): link the points to a promo window when kept_tagged.
Request
Responses
- 200
- 401
- 403
- 422
- 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.
Validation failed — the body is a field → messages map (Laravel shape) or the platform envelope with a stable machine-readable code. Fix the payload and resubmit.
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.