List All Users
Query Parameters
Page number of records you wish to skip before selecting records. Final skipped records count would be limit * offset
.
Additional query in PlusAuth Query Language format.
Page number of records you wish to skip before selecting records. Final skipped records count would be limit * offset
.
Additional query in PlusAuth Query Language format.
Whether this End-User is blocked or not. If true
End-User will not be able to login.
End-User's e-mail address.
true
if the End-User's e-mail address has been verified; otherwise false
. If force_email_verification
is enabled in your tenant's settings, it will check this value of user while performing email verification checks.
Connection name
External user's id coming from the connection.
Mevcut Değerler: twilio
vonage
netgsm
3gbilisim
dataport
messagebird
custom
hotp
totp
native
expo
one-signal
aws_ses
postmark
sendgrid
sparkpost
smtp
custom-oauth2
amazon
apple
e-devlet
dribbble
dropbox
facebook
github
google
linkedin
microsoft
slack
spotify
twitter
saml
ldap
Mevcut Değerler: sms
otp
push
email
social
enterprise
PlusAuth user's id
Raw user object from the connection
User's last login datetime in the ISO 8601 format according to universal time
Failed login attempts of user. It will reset to 0
after successful login.
End-User's full name in displayable form including all name parts, possibly including titles and suffixes, ordered according to the End-User's locale and preferences.
End-User's preferred phone number. It will be stored in E.164 format.
true
if the End-User's phone number has been verified; otherwise false
. If SMS MFA is enabled this value will be used to determine whether End-User has verified it's phone or not.
URI reference of the End-User's profile picture.
End-User's username
Additional metadata for your End-User. It must be an object containing 10 fields at max with keys and values no more than 1024 characters. Values can be only one of the types string
, number
and boolean
. You can also use "null"
as value to make metadata consistent across other users.
City or locality component.
Country name component.
Identifier for user address. Example: Delivery Address
, Billing Address
etc.
State, province, prefecture or region component.
Full street address component, which MAY include house number, street name, Post Office Box, and multi-line extended street address information. This field may contain multiple lines, separated by newline characters.
Full street address component, which MAY include house number, street name, Post Office Box, and multi-line extended street address information. This field may contain multiple lines, separated by newline characters.
Zip code or postal code component.
End-User's birthday. ISO 8601:2004 YYYY-MM-DD format. The year may be 0000, indicating that it is omitted. To represent only the year, YYYY format is preferred.
Surname(s) or last name(s) of the End-User. Note that in some cultures, people can have multiple family names or no family name; all can be present, with the names being separated by space characters.
Short code of End-User's gender.
Given name(s) or first name(s) of the End-User. Note that in some cultures, people can have multiple given names; all can be present, with the names being separated by space characters.
End-User's locale. For example, en-US or fr-CA.
Middle name(s) of the End-User. Note that in some cultures, people can have multiple middle names; all can be present, with the names being separated by space characters. Also note that in some cultures, middle names are not used.
Casual name of the End-User that may or may not be the same as the given_name. For instance, a nickname value of Mike might be returned alongside a given_name value of Michael.
URI reference for the End-User's profile page.
URI reference for the End-User's Web page or blog.
String from zoneinfo time zone database representing the End-User's time zone. For example, Europe/Paris or America/Los_Angeles.