Deletes many item categories in one call.

POST /inventory/item-categories/bulk-delete

Group: Inventory › Item Categories · Operation ID: bulkDeleteItemCategories

Deletes many item categories in one call, all or nothing. Every id is resolved and reference-checked before the first delete: an id that matches nothing fails the call with NOT_FOUND, and a category still referenced by items or inventory transactions fails it with ITEM_CATEGORY_IN_USE. Both name the offending row's index, and nothing is deleted in either case.

The response echoes the deleted categories in input order. To delete one at a time, use DELETE inventory/item-categories/: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: bulkDeleteItemCategoriesInput.

Field	Type	Required	Description
`ids`	array of string	yes	The unique identifiers of the item categories to delete. If any id is unknown or its category is still referenced, the whole call is rejected and nothing is deleted.

Example:

{
  "ids": [
    "3b7d5e9c-1a24-4f80-9c6d-2e8f70b13a45",
    "e57a0d34-9f62-4b18-bc25-71a6e8039d4b"
  ]
}

Response

200 Success

Under data (bulkDeleteItemCategoriesOutput):

Field	Type	Required	Description
`deleted`	array of object	yes	The deleted item categories, in input order. Match rows to inputs by index.
`deleted[].id`	string	yes	The unique identifier for the deleted item category.
`deleted[].name`	string	yes	The display name the deleted category held, echoed so you can log the removal without a prior read.

Response headers

Idempotency-Replayed — Present and true only 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 as false.

Errors

Code	Status
`NOT_FOUND`	400
`ITEM_CATEGORY_IN_USE`	400
`ITEM_CATEGORY_HAS_CHILDREN`	400
`IDEMPOTENCY_KEY_CONFLICT`	409
`IDEMPOTENCY_PAYLOAD_MISMATCH`	422

Statuses

400 — Invalid request or business failure. Codes: NOT_FOUND, ITEM_CATEGORY_IN_USE, ITEM_CATEGORY_HAS_CHILDREN
401 — Missing or invalid access token
403 — Not authorized
404 — Not found
409 — 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 requests
500 — Internal server error