ADM-OPERATION-200 - Update a new Operation

put

https://example.com/v1/operations/{operationId}

Updates the metadata of an existing Operation (only if in DRAFT status).

Feature flag

Requires OPERATIONS to be active.

Access control

OPERATOR: can update any Operation.
ACCOUNT: can update only their own Operations if they have the OPERATIONS_UPDATE right and are attached to the effective store.

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.

Editable fields

names, descriptions, startDate, endDate, and custom field values.
type, externalId, status, and owner info are not editable.

Status constraint

Only Operations in DRAFT status can be updated.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Path Params

operationId

string

required

Body Params

customFieldValues

array of objects

Array of custom field id and custom field value

customFieldValues

descriptions

object

Optional translated descriptions keyed by IETF BCP 47 locale; each provided locale must be allowed for the store

endDate

date-time

Planned activation end date

names

object

required

Translated names keyed by IETF BCP 47 locale; each provided locale must be allowed for the store

startDate

date-time

required

Planned activation start date

Headers

dj-client

string

enum

required

Specifies the client type making the request.

OPERATOR: Platform operator user.
ACCOUNT: Customer account user.
SUPPLIER: Supplier managing orders.

Allowed:

dj-api-key

string

required

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

dj-store

string

(Optional) Store ID in multi-store environments.

dj-store-view

string

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

Responses

201

Operation successfully updated

204

No Content

400

Invalid request payload.

Missing or invalid fields
Invalid date range (startDate must be ≤ endDate)
Invalid locale (provided locale not allowed for the store)

401

Authentication failed

403

Forbidden.

Unauthorized client value (unexpected dj-client)
Access denied (missing OPERATIONS_UPDATE or not attached to the effective store)
Feature flag OPERATIONS is disabled

404

Operation not found.