Rebalance Coverages
POST/api/v2/inventory-allocations/rebalance-coverages
Dispatches a background job that rebalances allocation coverages — it tears down every non-tight AwaitingReceipt coverage and rebuilds it from scratch using the current resolved PO ETAs (inbound-shipment expected arrival, falling back to the PO header's estimated delivery date).
orders:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Manually pinned (tight) coverage is never touched. Returns a tracked_job_log_id for monitoring progress via the tracked job log endpoints.
Use this after PO ETAs change so existing PO-line ↔ allocation bindings reflect earliest-ETA-first ordering.
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.