Claim Missing Units from Vendor
POST/api/repairs/vendor-dispatches/:dispatch/missing-claim
Claim Missing Units from Vendor.
repairs:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Raises a draft recovery claim against the vendor for units it never returned. Allowed when the dispatch is partially received, or shipped and past its expected_back_on date with nothing back (is_overdue is true); otherwise returns 422. The dispatch's missing_line_ids lists the claimable units.
Request fields:
line_ids(required): array, min:1line_ids.*(optional): integer, distinctnotes(optional): string, max:5000
Permission: repairs.recovery.
Authentication: Bearer token with the repairs:read / write scope.
Request
Responses
- 200
- 401
- 403
- 404
- 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.
Not found — no record with the given identifier (or the route does not exist). Verify the ID before retrying.
Unprocessable Content
Response Headers
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.