Deletes several account determination rules in one call.

POST /inventory/account-determination-rules/bulk-delete

Group: Inventory › Account Determination Rules · Operation ID: bulkDeleteAccountDeterminationRules

All or nothing. If any identifier matches no rule, nothing is deleted and the whole call fails, and index on the error says which entry. A rule is configuration, not a record other rows point at, so there is no in-use guard: an identifier that resolves is deleted, and its reason-code overrides go with it. The response is the deleted rules in the same order as the input. Use DELETE inventory/account-determination-rules/:id to delete a single rule.

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: bulkDeleteAccountDeterminationRulesInput.

Field	Type	Required	Description
`ids`	array of string	yes	The unique identifiers for the rules to delete. If any identifier matches nothing, nothing is deleted and the whole call fails.

Example:

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

Response

200 Success

Under data (bulkDeleteAccountDeterminationRulesOutput):

Field	Type	Required	Description
`deleted`	array of object	yes	The deleted rules, in the same order as the input. Match entries to inputs by index.
`deleted[].id`	string	yes	The unique identifier for the deleted rule.
`deleted[].ruleName`	string	yes	The label the deleted rule held.

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
`IDEMPOTENCY_KEY_CONFLICT`	409
`IDEMPOTENCY_PAYLOAD_MISMATCH`	422

Statuses

400 — Invalid request or business failure. Codes: NOT_FOUND
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