Search Warehouse Transfers
POST/api/v2/warehouse-transfers
Returns the same paginated list of warehouse transfers as the GET version of this endpoint, but accepts filters as a JSON request body instead of the query string. Use this POST variant when the filter set is too large or too complex to fit in a URL. The response includes an unfiltered_total alongside the standard paginator totals so clients can show both the filtered and total record counts.
warehouses:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Provide advanced filters under filter_groups, a tree of conditions combined with a conjunction of and or or. Each condition names a column, an operator, and a value. A free-text search term matches against transfer id, transfer number, source and destination warehouses, item SKU, and item FNSKU.
Text and status columns (transfer_status, shipment_status, receipt_status, from_warehouse, to_warehouse) accept: is, is_not, contains, does_not_contain, starts_with, ends_with, is_empty, is_not_empty, is_one_of, is_not_one_of.
Numeric and date columns (id, transfer_date, created_at, updated_at) accept: is, is_not, greater_than, greater_than_or_equal, less_than, less_than_or_equal, between, is_empty, is_not_empty. The transfer_type filter accepts standard, fba_inbound, awd_inbound, or awd_fba_replenishment; has_blemished, has_inbound_plan, archived, and include_deleted are boolean toggles. Custom field filters are also supported.
Sortable columns (via sort, prefix with - for descending): id, warehouse_transfer_number, transfer_date, transfer_status, shipment_status, receipt_status, created_at, updated_at, eta, archived_at, asn_last_sent_at, from_warehouse_name, to_warehouse_name. Results default to -transfer_date.
Request
Responses
- 200
- 401
- 403
- 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.
Validation failed — the body is a field → messages map (Laravel shape) or the platform envelope with a stable machine-readable code. Fix the payload and resubmit.
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.