Get Bill of Lading
GET/api/amazon/:integrationInstance/draft-inbound-plans/:draft_inbound_plan/shipments/:plan_shipment/bill-of-lading
Fetch the bill of lading (BOL) document for a confirmed freight shipment via the Amazon Fulfillment Inbound v0 getBillOfLading operation.
This endpoint currently requires session authentication; Personal Access Token scope support is in progress.
Amazon only issues a BOL for shipments booked with an Amazon-partnered carrier. When the shipment's confirmed transportation option uses the seller's own carrier (USE_YOUR_OWN_CARRIER), Amazon returns an empty payload indefinitely, so this endpoint short-circuits without calling Amazon and returns 200 with available: false and a message naming the carrier that does supply the BOL. Booking a carrier named "Amazon Freight" directly is still a non-partnered booking — the program decides, not the carrier name.
For a partnered shipment whose document Amazon has not produced yet (or a 404/empty response), the endpoint returns 200 with available: false and a "not yet available" message rather than an error. When the BOL is available the response carries the download url, available: true, and a label_print_id (recorded in the label-print audit trail as kind BOL).
Returns 404 when the shipment does not belong to the draft inbound plan.
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.