...
Name | Accepted Values | Multivalued | Mandatory | Default | Description | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
<any user attribute name> | String |
|
|
| Include only users with exact matching search criteria value for the specified attribute name(s). You may use any of the builtin or custom attribute names here. The value given is searched from the attribute defined. You may use multiple different attribute names (and limiting search criteria values) in a single query (all must then match for the result to be returned). You cannot use the same attribute name multiple times in a single query. You can also search by user status. Values for user status are: 0=Pending, 1=Enabled, 2=Disabled, 3=Locked. You can also use the textual values instead of the integers. For example "Pending" is equally suitable as "0". | ||||||||||||
lastModifiedStart | Timestamp | This will limit the returned users to those with a last modified time later than the given cutoff value. The last modified time for the user changes when:
The last modified time for the user does not change when:
Note: You currently cannot get a listing of users that have been deleted from the system. You need to check the audit logs for those. | lastModifiedEnd | Timestamp | This will limit the returned users to those with a last modified time earlier than the given cutoff value. | createdStart | Timestamp | This will limit the returned users to those with a created time later than the given cutoff value. | createdEnd | Timestamp | This will limit the returned users to those with a created time earlier than the given cutoff value. | maxResults | Integer |
|
| No Limit | Limit the maximum number of results. |
exactMatch | Boolean |
|
| false | When limiting attribute values are used, this parameter defines if the value must be found exactly like given (true) or if the database value just needs to start with the given value (false). |
...