ADM-OPERATOR-USER-251 - Replace Operator User Stores

Overview
Replaces the list of stores assigned to the operator user identified by operatorUserId.

User scoping
Admin endpoint. Only operator users can call this endpoint (dj-client: OPERATOR).

Store scoping
The effective store context is derived from the dj-store and dj-store-view headers when provided. This context does not impact store assignment.

Replacement rules
Store access is always explicit:
- If the request body contains an empty array: the operator user has no store access (restricted from all stores).
- If the request body contains store external IDs: the operator user is restricted to those stores only.
- Duplicates in the request are ignored.

Errors
Returns validation errors (400), authentication errors (401), authorization errors (403), not found (404), and unexpected server errors (500).

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required

Operator user identifier.

Body Params
storeExternalIds
array of strings
required
storeExternalIds*
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

No Content (store assignment replaced)

400

Bad request (invalid payload)

401

Unauthorized (invalid or missing API key)

403

Forbidden (insufficient permissions)

404

Not found (unknown operator user)

500

Internal server error

Language
Credentials
Bearer
JWT
LoadingLoading…
Response
Click Try It! to start a request and see the response here!