put https://example.com/v1/operations//accounts
Adds one or more accounts to a PRIVATE Operation to control visibility.
Feature flag
- Requires
OPERATIONS_ENABLEDto 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_ACCOUNTSpermission.
Store scoping
- Effective store is the
dj-storeheader if provided, otherwise the tenant default store. - ACCOUNT must be attached to the effective store; otherwise 403.
Constraints
- Only
DRAFTOperations are editable. - Only
PRIVATEOperations accept account associations. - Request body must be a non-empty array of
accountExternalIdstrings. - Already linked accounts are ignored.
- Unknown accounts are ignored.
- If none of the provided IDs are valid, the API returns 404.
