List Reimbursement Cases
GET/api/amazon/unified/reimbursement-cases
Lists reimbursement cases across Amazon integration instances, paginated. Default order is by urgency (soonest filing deadline first, then largest amount).
recovery:readGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Filters: lifecycle group, status, category, instance, currency, assignee (id, me, none), due within N days, missing cost, case text source, and a search across case ID, SKU, FNSKU, ASIN, Amazon case ID and evidence order/shipment IDs. Advanced text/numeric/date operator filters are supported (see query parameters).
Each case includes its plain-language status label, lifecycle group, days left to file, the one-sentence explanation (why) and evidence rows, case text and provenance, Seller Central filing guidance, and allowed status transitions.
Other per-case fields:
informational—truefor a heads-up case that can't be filed with Amazon (e.g.reimbursed_then_returned: Amazon is expected to take a reimbursement back because the item was returned). Informational cases never reachready_to_submitorsubmitted, are left out of the filing queue, and always havecan_submit_now: false.allowed_transitions— the statuses this case can move to, taking its category into account (informational cases never listready_to_submitorsubmitted).can_submit_now— whether the case can be filed today: not informational, its claim window has opened and it has not expired.outstanding_amount— the claim value not yet covered by cash paid or inventory returned (0for a case Amazon paid automatically).inventory_restitution_value— the value of units Amazon returned to your inventory against the filed claim, at the claim's unit value. List rows leave outclaim_text_facts(the fact sheet the case text was written from); it is returned by Get Reimbursement Case and Get Filing Session Queue.
Rows with status ready_to_submit also carry proof_of_ownership (see Get Reimbursement Case), so a ready case still missing its supplier invoice can be shown as needing one.
Request
Responses
- 200
- 401
- 403
- 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.
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.