Resolve Discrepancy Item
POST/api/amazon/:integrationInstance/draft-inbound-plans/:draft_inbound_plan/tracking/items/:shipment_item/resolve
Acknowledge (resolve) a shipment item's discrepancy with a note — e.g. after filing an Amazon reimbursement case for a SHORT item. Resolution is an overlay: it stamps discrepancy_resolved_at and resolution_note but leaves discrepancy_status untouched. Resolved items drop out of the tenant-level discrepancies report (unless filter[resolved]=1). Reversible via Unresolve Discrepancy Item.
Any valid API token can call this endpoint — no specific scope required. Manage tokens.
Resolvable statuses: SHORT, OVER, and PENDING. Items with no discrepancy (MATCH or null status) return a 422.
Fields:
resolution_note(string, required, max 1000) — why/how the discrepancy was handled
Response: the updated reconciliation item payload (same shape as the Get Reconciliation items).
Errors:
- 404 — the shipment item does not belong to this draft inbound plan
- 422 — the item has no discrepancy to resolve (status
MATCHor null) - 422 —
resolution_notemissing or longer than 1000 characters
Authentication: Bearer token (PAT).
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 Entity
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.