Get Reimbursement Case
GET/api/amazon/unified/reimbursement-cases/:reimbursementCase
Returns one reimbursement case with its integration instance, assignee, product and matched Amazon reimbursements, plus attachments — the files to attach when filing (see List Reimbursement Case Attachments).
recovery:readGrant this scope to your token under Settings → Developer → Personal Access Tokens.
The case carries the same per-case fields as List Reimbursement Cases, including informational, category-aware allowed_transitions, can_submit_now, outstanding_amount and inventory_restitution_value.
Each entry in reimbursements is a whole Amazon reimbursement row plus an allocation object — the share of that row allocated to this case:
kind—pre_filing(Amazon paid before the case was filed; already taken off the claim),payment(Amazon paid against the filed claim) orreversal(Amazon took back an earlier allocation; negative quantity and amount).quantity— units allocated to this case.quantity_inventory— of those, units returned to inventory rather than paid in cash.amount— the cash amount allocated to this case.parent_allocation_id— for a reversal, the allocation it reverses; otherwisenull.
One reimbursement row can be split across several cases, so an allocation can be smaller than the row's totals.
filing_guidance.url is where to file the claim in the marketplace's Seller Central. For an inbound shortage with a shipment ID it opens that shipment's Contents page (/fba/inbound-shipment/summary/{shipment_id}/contents); otherwise it is the category's general page.
marketplace_country is the marketplace the claim's money came from, taken from the case currency (a CAD claim on a North America account is CA), falling back to the account's primary marketplace. Every Seller Central link on the case uses that marketplace's host.
filing_guidance.assistant is set for claims Amazon takes through Seller Assistant, its support chat. It holds topic (a topic to pick, or null), say (the opening message), asks_for (the ID the assistant asks for), asks_for_value (that ID from this case, or null), opens (the name of Amazon's own tool the chat opens for this claim, or null), steps (in order, the steps inside that tool: {confirm, value} an ID to check the tool shows, {pick, when?} an option to choose, {enter, value} a field and this case's value, formatted as Amazon's form accepts it (e.g. 18.0), {choose} a choice only the seller can make, {submit} the button that sends the request) and agent_request (the message that asks for a support agent; null when the claim is filed in the tool). It is null for claims filed elsewhere.
filing_facts lists every detail Seller Assistant or a support agent may ask for, as {label, value} pairs (for example FNSKU, ASIN, Amazon order ID, Reference ID (TRID), event date, units, amount requested, and for fee claims the correct and recorded measurements and fees). It is returned by this endpoint only, not by the list.
filing_guidance.check says where to confirm Amazon hasn't already handled the claim before filing: tool (its claim tool lists each unit as Reimbursed, Found or Eligible; used for lost units) or portal.
filing_guidance.tool is set when Amazon files the claim in its own claim tool, which sits at the bottom of the category's FBA inventory reimbursement policy page (filing_guidance.url). This is currently offered in the US marketplace. It holds name (the tool's title on the page) and steps in order: {pick} (an option to choose) or {enter, value} (an ID to enter, with this case's value). filing_guidance.switch_marketplace names the marketplace to pick in Seller Central's header when it is reached through another marketplace's Seller Central, for example Canada through sellercentral.amazon.com.
filing_guidance.account is the marketplace's name in Amazon's "Select an account" list (for example United States), which Seller Central shows on a fresh visit.
filing_guidance.portal is set for claims Amazon tracks in its Inventory Defect and Reimbursement portal (customer returns and warehouse lost, damaged or disposed claims). It holds url (the portal's Resolved list), in_progress_url (its In progress list), search (what to search by: Order ID or FNSKU), box (which search takes it: filter, the search at the top of the page, for an FNSKU; table, the search above the list, for an order ID) and value (this case's ID). Check it before filing: a claim listed under Resolved is already settled, and one listed under In progress is already being investigated.
proof_of_ownership — whether the supplier's invoice Amazon wants as proof of ownership is on file (null when the case's category doesn't need one):
on_file(boolean) — true when an invoice file is ready to attachgap(string|null) — why it is missing:no_purchase_order(the product was never bought on a purchase order),no_invoice(the purchase order has no supplier invoice) orno_file(the invoice has no file)message(string) — the gap in plain words, empty when on filestores_on(string) — where an uploaded invoice is kept:purchase_orderorproductpurchase_order(object|null) —idandnumberof the purchase order the case citesuploaded(object|null) —file_nameanduploaded_atof an invoice uploaded with Upload Reimbursement Case Supplier Invoice
Case history and revaluation:
amazon_cases— every Seller Central case the opportunity was worked on, oldest first:amazon_case_id,kind(claim,appeal,revaluation,other),kind_label,filed_at,filed_by, andis_current(the case inamazon_case_id, the one Amazon is working now).revaluation— set once Amazon has paid on a filed case (statussubmitted,partially_reimbursedorreimbursedwith a payment):urlof Amazon's Reimbursement Revaluation Tool for the marketplace and thereimbursement_idsto give it.nullotherwise. Amazon only raises a reimbursement through that tool, which opens a new case.
Request
Responses
- 200
- 401
- 403
- 404
- 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.
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.