ADM-OPERATION-251 - Add accounts to a PRIVATE Operation

put

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

Adds one or more accounts to a PRIVATE Operation to control visibility.

Feature flag

Requires OPERATIONS_ENABLED to be active.

Access control

OPERATOR: can add any account to any PRIVATE Operation.
ACCOUNT (FOC): can add accounts only on Operations they own (ownerId = customerUserId) and if they have the OPERATIONS_ADD_ACCOUNTS permission.

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 DRAFT Operations are editable.
Only PRIVATE Operations accept account associations.
Request body must be a non-empty array of accountExternalId strings.
Already linked accounts are ignored.
Unknown accounts are ignored.
If none of the provided IDs are valid, the API returns 404.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Responses

204

Accounts successfully processed

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.
— Unexpected value for field dj-client, must be one of [OPERATOR, ACCOUNT].
— Permission denied. Caller is not allowed to modify this Operation (missing OPERATIONS_ADD_ACCOUNTS right, not owner, or not attached to store).
— Only DRAFT operations can be updated.
— Operation type must be PRIVATE to manage account associations.
— Feature Flag disabled for this feature.

404

Not found.

Operation not found
None of the provided accountExternalIds exist for this Operation.

500

Unexpected server error.