Changes 2025.09.03
What's Changed
GET
/api/identity-store/stores/{storeName}/users
Return Type:
Changed response : 200 OK
The List Users endpoint is in early access. We have made the following change to the 200 Response to improve performance. Customers may need to update their integration if using this API.
- Changed content type :
application/json
- Changed property
content
(array)
Changed items (object): > A user search dto - data needed for users search view. Use the GET /users API to retrieve additional data.
- Added property
storeId
(string) > The id of the store in which this user resides. - Deleted property
type
(string) > A user type supplied by the customer. - Deleted property
locale
(object) > Locale information. Exposes the language, country and variant locale components, for exampleen_US_UNIX
contains these components asen
,US
andUNIX
respectively. - Deleted property
timezone
(string) > The user's timezone. The default timezone configured at the store level. - Deleted property
firstName
(string) > The user's first name. - Deleted property
lastName
(string) > The user's last name. - Deleted property
email
(string) > The user's email address. - Deleted property
dateOfBirth
(string) > The user's date of birth. - Deleted property
nationalities
(array) > A list of nationalities associated with the user. - Deleted property
attributes
(object) > A list of attributes associated with the user. > > One attribute, which is set internally by the server on a user during passkey registration, ispasskeyUsers
. A specific user handle may be provided via the passkey registration request, if not it is set to a random ID when the first passkey is created for the user. The attribute value looks like this:. > >"passkeyUsers": { > "{relyingPartyId}": { > "USER_HANDLE":"{passkey user handle}" > } > } >
- Deleted property
summaryInfo
(object) > Summary information about items registered to the user such as biometrics, device keys and passkeys. - Deleted property
locks
(object) > User lock information. > > Describes locks at the user level and modality level. A user can have escalating temporary locks which come into effect after a certain number of consecutive authentication attempts. The number of locks and the lock durations are configured at the store level. > > NOTE: Currently only user-level locking is supported with modality level locking planned for a later release. - Deleted property
lockedUntilDtm
(string) > If the user is currently locked, this is the time at which the lock will end. - Deleted property
lastAuthenticatedDtm
(string) > If the user has been authenticated, this is the time at which they were last authenticated.
GET
/api/arthr/apiKeys
Parameters:
Changed: size
in query
GET
/api/metrics-server/auditMessages/queries/{executionId}/result
Parameters:
Added: size
in query