Get FBA Loss Event Status Summary
GET/api/amazon/unified/fba-loss-events/summary
Totals FBA loss events by status — where your lost units went. Losses that are cash only (no unit was lost) are left out. Events are selected by loss date.
This endpoint currently requires session authentication; Personal Access Token scope support is in progress.
Query parameters (all optional):
integration_instance_ids— comma-separated Amazon integration IDs.date_from,date_to— loss date range (m/d/Y);date_tomust be on or afterdate_from.
Fields:
cost_currency— the currency ofcost(your base currency).statuses— one entry per status that has events:status(researching, confirmed_lost, partially_reimbursed, reimbursed, found, reversed, written_off),events,units_lost,units_found,units_cash_reimbursed,units_replaced,units_reversed, andcost— the FIFO cost the lost units consumed (null when none is known).units_found_net,units_paid_net,units_outstanding— each lost unit counted exactly once: found again, paid for (cash or replacement, net of reversals), or still outstanding. The three add up tounits_lost; the grossunits_*counts above can overlap.
Request
Responses
- 200
- 401
- 403
- 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.
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.