Skip to main content

List Unattributed AWD Departures

GET 
/api/amazon/:integrationInstance/awd/ledgers/unattributed-departures

AWD departures that could not be attributed to an FBA shipment.

Amazon records many departures against its own outbound order id (repl-ship-<uuid>), or against nothing at all, so they cannot be matched to a shipment by id and the warehouse transfer they belong to never closes. This is the residue those id paths cannot reach, with why each one stopped and what it could have matched.

reason is one of:

  • ambiguous — several shipments are equally good evidence. Nothing is chosen automatically, because picking one would attribute the cost by coin toss.
  • quantity_mismatch — a shipment matches on product and timing but not on quantity. Never applied automatically: a partial-quantity link is the most likely way to attribute cost to the wrong transfer.
  • no_transfer — a shipment matches, but has no open warehouse transfer to close.
  • no_candidate — nothing AWD-sourced with this product left within the window.

will_auto_attribute is true when the departure DOES match cleanly and is simply waiting for the next scheduled pass — it is not waiting on a person, and its reason is null.

⚠ returned is how many are in this response; totals.unattributed is how many there really are. They differ once the limit bites. totals.resolved_by_reference counts departures Amazon's own reference already resolved — neither outstanding nor attributed here. by_reason_shown is counted across the rows RETURNED, not the whole residue.

Authentication: requires a Bearer token.

Not yet available to API tokens

This endpoint currently requires session authentication; Personal Access Token scope support is in progress.

Request​

Responses​

OK

Response Headers
    Content-Type