Delete Warehouse
DELETE/api/warehouses/:warehouse
Deletes a warehouse. A warehouse still referenced by other records cannot be deleted: sales order lines and fulfillments, fulfillment orders, purchase orders, inbound shipments and receipts, inventory movements and FIFO layers, inventory adjustments and assemblies, stock takes, manufacturing orders, warehouse transfers, RMAs and return receipts, sales credits, vendor credit shipments, vendor returns and their shipments, POS register sessions, Amazon pending inbounds, suppliers using it as their default warehouse, or a connected integration. The 400 response lists each blocking record type under errors. If the database still refuses the delete for any other linked record, the endpoint returns 400 and nothing is deleted. Use Check Warehouses Deletable first to see every blocker.
warehouses:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Authentication: Requires Bearer token.
The default returns warehouse cannot be deleted (400).
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 429
OK
Response Headers
Bad Request
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.