Deletes several shipments in one call.
POST /inventory/shipments/bulk-delete
Group: Inventory › Shipments · Operation ID: bulkDeleteShipments
All or nothing: if any identifier matches no shipment, or names one past draft, nothing is deleted. index on the error says which, counting from zero. Delete one at a time with DELETE inventory/shipments/:id.
Open in the interactive reference
Parameters
| Name | In | Type | Required | Description |
|---|---|---|---|---|
Api-Version |
header | "v1" |
yes | The API version this request targets, named by its public identifier. Required on every request; omitting it, or naming a version this company does not have, is answered with 400. This document describes version v1. |
Idempotency-Key |
header | string | no | An opaque caller-chosen string (1-255 characters) that makes this request safe to retry. Repeating the same key with an identical request body replays the original response instead of re-executing - but only once that original request succeeded; a failed attempt re-executes on retry. Repeating the key with a different body is answered with 422. A key still in flight is answered with 409 - as is a key whose original request was interrupted before it finished, for a few minutes afterwards, until that attempt is presumed dead. A completed response stays replayable for 24 hours. The key is scoped to the caller, not to the action: reusing it for a different action is answered with 409 or 422 rather than treated independently. On read actions this header is ignored. On write actions that cannot offer the guarantee it is answered with 400 IDEMPOTENCY_NOT_SUPPORTED rather than silently ignored. |
Request body
Required, application/json: bulkDeleteShipmentsInput.
| Field | Type | Required | Description |
|---|---|---|---|
ids |
array of string | yes | The unique identifiers of the shipments to delete. All or nothing: if any is missing or past draft, none is deleted. |
Example:
{
"ids": [
"3b7d5e9c-1a24-4f80-9c6d-2e8f70b13a45",
"e57a0d34-9f62-4b18-bc25-71a6e8039d4b"
]
}
Response
200 Success
Under data (bulkDeleteShipmentsOutput):
| Field | Type | Required | Description |
|---|---|---|---|
ids |
array of string | yes | The unique identifiers of the deleted shipments, in input order. |
Response headers
Idempotency-Replayed— Present andtrueonly when this response replays a previously stored one for the same Idempotency-Key, rather than reflecting a live execution. Absent on a live response - never sent asfalse.
Errors
| Code | Status |
|---|---|
NOTHING_TO_DELETE |
400 |
NOT_FOUND |
400 |
WRONG_STATUS |
400 |
POSTING_REJECTED |
400 |
IDEMPOTENCY_KEY_CONFLICT |
409 |
IDEMPOTENCY_PAYLOAD_MISMATCH |
422 |
Statuses
400— Invalid request or business failure. Codes: NOTHING_TO_DELETE, NOT_FOUND, WRONG_STATUS, POSTING_REJECTED401— Missing or invalid access token403— Not authorized404— Not found409— The Idempotency-Key is still being processed by another request.422— The Idempotency-Key was already used with a different request payload.429— Too many requests500— Internal server error