Get Shipment Board
GET/api/amazon/:integrationInstance/draft-inbound-plans/:draft_inbound_plan/tracking/board
Post-ship shipment board for a draft inbound plan: every shipment of the plan's confirmed placement option with its items, extended with the Phase 7 monitoring fields. Data is refreshed hourly by the scheduled amazon:fba-inbound:sync-shipments sweep (and on demand via Refresh Shipment).
Any valid API token can call this endpoint — no specific scope required. Manage tokens.
Board-only fields (on top of the standard plan-shipment payload):
days_since_shipped(integer|null) — whole days sinceshipped_at; null when not yet marked shippedunits_shipped/units_received(integer) — sums of the item quantitiesboxes_count(integer) — number of boxes on the shipmentclaim_deadline(date|null) —shipped_at+ 60 days (Amazon's reimbursement claim window, policy since Oct 2024); null when not shippedclaim_days_remaining(integer|null) — whole days untilclaim_deadline(negative once lapsed); null when not shippedreconciliation_status(string) — shipment-level rollup of the item discrepancy statuses:pending(nothing decided yet, or some items still PENDING/undecided),match(every item MATCH),short(any SHORT),over(any OVER),mixed(both SHORT and OVER present)
Discrepancy mapping (per item, recomputed on every sync):
amazon_statusNOT in (RECEIVING,CLOSED) →null(too early to judge)- received == shipped →
MATCH - received > shipped →
OVER - received < shipped and
amazon_status=CLOSED→SHORT(final shortage) - received < shipped and
amazon_status=RECEIVING→PENDING(still being received)
Responses include items (id, msku, fnsku, quantity_shipped, quantity_received). Pallets, transportation options, and delivery window options are NOT loaded on the board endpoint — use List Shipments (Placement & Transport) for those.
Authentication: Bearer token (PAT).
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.