Attribute AWD Departure To Shipment
POST/api/amazon/:integrationInstance/awd/ledgers/departure-links/:awdLedger
Attribute a departure to a shipment by hand, for the cases the evidence cannot settle on its own.
Recorded as manual rather than dressed up as evidence: a link a person made and one that was inferred carry different trust, and anyone auditing attribution later needs to tell them apart.
Refused (422) when the ledger row is not a DEPARTED event, when either the departure or the shipment is already attributed, when the shipment is not AWD-sourced on this integration or does not carry the departure's product, or when it has no open warehouse transfer — a link that closes nothing would use up that shipment's single claim for no benefit.
Quantity and the date window are deliberately NOT re-imposed here: a mismatched quantity or an unusual lag is exactly the judgement a person is making.
⚠ This LINKS records. It creates no ledger entry, stock layer or consumption, so AWD on-hand is unchanged.
Authentication: requires a Bearer token.
This endpoint currently requires session authentication; Personal Access Token scope support is in progress.
Request
Responses
- 200
- 401
- 403
- 404
- 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.
Not found — no record with the given identifier (or the route does not exist). Verify the ID before retrying.
Unprocessable Content
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.