| Field | Type | Required | Description | Example |
|---|---|---|---|---|
emailAddress |
List<String> | ➖ | Returns users with the specified email addresses. Accepts up to 100 email addresses. Any email addresses not found are ignored. |
|
phoneNumber |
List<String> | ➖ | Returns users with the specified phone numbers. Accepts up to 100 phone numbers. Any phone numbers not found are ignored. |
|
externalId |
List<String> | ➖ | Returns users with the specified external ids. For each external id, the + and - can beprepended to the id, which denote whether the respective external id should be included or excluded from the result set. Accepts up to 100 external ids. Any external ids not found are ignored. |
|
username |
List<String> | ➖ | Returns users with the specified usernames. Accepts up to 100 usernames. Any usernames not found are ignored. |
|
web3Wallet |
List<String> | ➖ | Returns users with the specified web3 wallet addresses. Accepts up to 100 web3 wallet addresses. Any web3 wallet addressed not found are ignored. |
|
userId |
List<String> | ➖ | Returns users with the user ids specified. For each user id, the + and - can beprepended to the id, which denote whether the respective user id should be included or excluded from the result set. Accepts up to 100 user ids. Any user ids not found are ignored. |
|
organizationId |
List<String> | ➖ | Returns users that have memberships to the given organizations. For each organization id, the + and - can beprepended to the id, which denote whether the respective organization should be included or excluded from the result set. Accepts up to 100 organization ids. |
|
query |
Optional<String> | ➖ | Returns users that match the given query. For possible matches, we check the email addresses, phone numbers, usernames, web3 wallets, user ids, first and last names. The query value doesn't need to match the exact value you are looking for, it is capable of partial matches as well. |
|
lastActiveAtSince |
Optional<Long> | ➖ | Returns users that had session activity since the given date, with day precision. Providing a value with higher precision than day will result in an error. Example: use 1700690400000 to retrieve users that had session activity from 2023-11-23 until the current day. |
1700690400000 |
limit |
Optional<Long> | ➖ | Applies a limit to the number of results returned. Can be used for paginating the results together with offset. |
|
offset |
Optional<Long> | ➖ | Skip the first offset results when paginating.Needs to be an integer greater or equal to zero. To be used in conjunction with limit. |
|
orderBy |
Optional<String> | ➖ | Allows to return users in a particular order. At the moment, you can order the returned users by their created_at,updated_at,email_address,web3wallet,first_name,last_name,phone_number,username,last_active_at,last_sign_in_at.In order to specify the direction, you can use the +/- symbols prepended in the property to order by.For example, if you want users to be returned in descending order according to their created_at property, you can use -created_at.If you don't use + or -, then + is implied. We only support one order_by parameter, and if multiple order_by parameters are provided, we will only keep the first one. For example,if you pass order_by=username&order_by=created_at, we will consider only the first order_by parameter, which is username. The created_at parameter will be ignored in this case. |