Customer User
Definition
A Customer User is an entity that represents a customer user on the DJUST platform. It is defined by the following information:
- Last Name
- First Name
- Email Address (mandatory, editable after creation, must be unique)
- Group (which carries access rights)
Creating a Customer User
To create a Customer User, the following information is required:
- A last name and a first name
- A valid email address
- A defined group that manages their access rights
- An account to which they are linked (mandatory)
Without this information, the Customer User cannot be created.
Modifications and Restrictions
Once created, a Customer User can be modified. The following fields can be updated:
- First name, last name, group — can be updated at any time.
- Email address — can be updated via the admin API (
PUT /v1/customer-users/USERID). The new email must be unique across all Customer Users. If the email is empty or not provided in the request, the existing email is preserved.
Filtering the Customer User list
The customer user list can be narrowed on account, status, users without an account, free-text search, the current store and, since 3.139, on two date ranges:
- Creation date
- Update date
They behave like the date filters of the other Back-Office lists — the customer account list and the quote list in particular: same way of picking a period, same rules on the bounds. Once applied, each range is shown as a removable tag above the table and is kept in the page URL, so a filtered view can be shared as a link or survive a reload.
Filtering via API
fetchCustomerUsers (GET /v1/customer-users) — Access: dj-client: OPERATOR
| Parameter | Description |
|---|---|
creationDateFrom / creationDateTo | Keeps the customer users created at or after / at or before this instant |
updateDateFrom / updateDateTo | Keeps the customer users updated at or after / at or before this instant |
- Dates are ISO-8601 instants. Each bound is optional and included.
- A range whose start is after its end returns an empty page, not an error. A date that cannot be read is rejected with a
400(TMI0001). - The update date is the one of the user record: it equals the creation date until the user is first updated, and moves with a status change, the user's first password, an update of the user, or a change of its customer accounts. Changing the user's groups does not move it.
- All filters combine with each other, with the search and with the current store.
GET /v1/customer-users?creationDateFrom=2026-01-01T00:00:00Z&creationDateTo=2026-01-31T23:59:59Z&status=ACTIVE
dj-client: OPERATOR
dj-api-key: <your-api-key>
Tip: PairupdateDateFromwith a status filter to list the users activated since your last synchronization, without exporting the whole list.
Updated 9 days ago

