ADM-OPERATION-350 - Remove variants from an Operation

Removes one or more variants from a specific Operation.

Feature flag

  • Requires OPERATIONS to be active.

Access control

  • OPERATOR: can remove variants from any Operation (no store constraint).
  • ACCOUNT: can remove variants only from Operations they own (ownerId = customerUserId) and if they have the OPERATIONS_UPDATE right.

Store scoping

  • Effective store is the dj-store header if provided, otherwise the tenant default store.
  • ACCOUNT must be attached to the effective store; otherwise 403.

Constraints

  • Only Operations in DRAFT status accept line removals.
  • Request body must be a non-empty array of external variant identifiers (strings).
  • Unknown variantId values are ignored; processing continues.
  • If none of the provided variantId values are valid for the Operation, the API returns 404.
Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required

Operation identifier to remove variants

Body Params
variantIds
array of strings
required

Non-empty array of external variant identifiers to remove

variantIds*
Headers
string
enum
required

Specifies the client type making the request.

  • OPERATOR: Platform operator user.

  • ACCOUNT: Customer account user.

  • SUPPLIER: Supplier managing orders.

Allowed:
string
required

API key required for authentication. Must be valid and linked to the requesting user.

string

(Optional) Store ID in multi-store environments.

string

(Optional) Store view ID in multi-store environments.

Responses
204

Variants successfully removed from the Operation.

400

Invalid payload.

  • Request body must be a non-empty array of strings
  • Wrong format for one or more items
401

Unauthorized. Missing or invalid authentication token.

403

Forbidden. One of the following applies:

  • Unauthorized client value (unexpected dj-client)
  • Permission denied (missing OPERATIONS_UPDATE, not owner)
  • Store access denied (ACCOUNT not attached to effective store)
  • Invalid status (only DRAFT Operations can be modified)
  • Feature disabled
404

Not found.

  • Operation not found
  • All provided variantIds are unknown for this Operation
Language
Credentials
Bearer
JWT
LoadingLoading…
Response
Click Try It! to start a request and see the response here!