Get Warehouse Transfer
GET/api/v2/warehouse-transfers/:warehouseTransfer
Returns the full detail view of a warehouse transfer.
warehouses:readGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Eager-loads: from_warehouse, to_warehouse, tags, adjustments, shipments (with lines and receipts), financial_lines, and COGS data. Also preloads current stock levels for both warehouses.
For transfers with an Amazon FBA destination, the response includes back-links to the Amazon records the transfer materializes: amazon_inbound_shipment (the FBA inbound shipment) and amazon_inbound_plan (the FBA inbound plan it was built from). Each carries an integration_instance_id, which identifies the Amazon account the record belongs to. Both are omitted when the transfer has no Amazon destination.
amazon_inbound_shipment.is_legacy tells you which shipment detail endpoint to call for it: true means the record is a legacy FBA inbound shipment, retrievable at GET /api/amazon/{integrationInstance}/inbound/shipments/{shipment}; false means it is a current-format shipment, retrievable at GET /api/amazon/{integrationInstance}/new-inbound/shipments/{shipment}. The two record sets use independent id sequences, so the same id can exist in both — always branch on this flag rather than assuming a format.
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.