Skip to main content

List Reimbursement Cases

GET 
/api/amazon/unified/reimbursement-cases

Paginated list of SKU.io-tracked FBA reimbursement claim cases, unified across all Amazon integration instances. Cases are flagged by automated detectors (lost or damaged warehouse inventory, customer returns never received back, inbound shortages, fee overcharges, etc.) and move through a claim lifecycle: potential, under_review, ready_to_submit, submitted, partially_reimbursed, reimbursed, denied, dismissed, expired.

Authorization

Any valid API token can call this endpoint — no specific scope required. Manage tokens.

Pagination: page and per_page (default 10). Sorting: sort=<field> ascending or sort=-<field> descending. Sortable fields: id, category, status, amazon_case_id, flagged_at, submitted_at, reconciled_at, claim_window_expires_at, sku, fnsku, asin, quantity, unit_cost, potential_amount, reimbursed_amount, currency, created_at, updated_at.

Simple filters:

  • filter[search] — fuzzy search across amazon_case_id, sku, asin, fnsku and the integration instance name. Restrict with search_columns and force exact matching per column with search_strict_columns.
  • filter[integration_instance_ids] — comma-separated Amazon integration instance IDs.
  • filter[statuses] — comma-separated list of statuses (potential, under_review, ready_to_submit, submitted, partially_reimbursed, reimbursed, denied, dismissed, expired).
  • filter[categories] — comma-separated list of categories (warehouse_lost, warehouse_damaged, customer_return_not_received, customer_return_damaged, customer_return_refund_mismatch, inbound_shortage, removal_order_discrepancy, fba_fee_overcharge, chargeback_reversal, destroyed_without_authorization).
  • filter[expiring_within_days] — only cases whose claim window expires within the next N days (and has not already expired).

Advanced operator filters use the syntax filter[column.operator]=value; a bare filter[column]=value is treated as the is operator.

  • Text columns (amazon_case_id, sku, fnsku, asin, category, status, currency, unit_cost_source) support: contains, does_not_contain, is, is_not, is_one_of, is_not_one_of, starts_with, does_not_start_with, ends_with, does_not_end_with, is_empty, is_not_empty.
  • Numeric columns (quantity, unit_cost, potential_amount, reimbursed_amount) support: is, is_not, is_one_of, is_not_one_of, greater_than, less_than, greater_than_or_equal, less_than_or_equal, between, is_empty, is_not_empty.
  • Date columns (flagged_at, submitted_at, reconciled_at, claim_window_expires_at, created_at, updated_at) support: is, is_not, before, after, on_or_before, on_or_after, between, is_empty, is_not_empty, today, yesterday, tomorrow, past_week, past_month, past_year, next_week, next_month, next_year, days_ago, days_from_now, past_days, next_days. Date values use ISO 8601 / Y-m-d; between takes two comma-separated values.

Complex AND/OR filter trees can be sent via filter_groups (base64-encoded JSON tree of conditions and nested groups).

Request​

Responses​

OK

Response Headers
    Content-Type