Find 'UserProfile' entities using the specified (query) parameters
GET/user-profile
Same as POST /find, but serializing the query in the 'q' parameter instead of the request body
Request
Query Parameters
The DataReadParams query as JSON or base64-encoded JSON - See POST route
Responses
- 200
- 4XX
- 5XX
Returns FindResult of type 'UserProfile' expanded with specified mapped values
- application/json
- Schema
- Example (from schema)
Schema
Array [
]
data
object[]
required
The unique entity id - must be a positive integer
If the entity has been soft-deleted this value is true
The creation time for this entity or mapping value
1970-01-01T00:00:00.000Z
The creator user id of this entity or mapping value - or zero if created by the system
0
The last modification time for this entity or mapping value
1970-01-01T00:00:00.000Z
The id of the user who last modified or undeleted this entity or mapping value - or zero if modified by the system
0
The soft-deletion time for this entity or mapping value
1970-01-01T00:00:00.000Z
The id of the user who deleted this entity or mapping value - or zero if deleted by the system
0
A tag for detecting conflicting modifications - current value (may be empty) must be passed along in an update (or update must be forced)
The global user id for this profile
The user's primary email address for this organization
An optional job title or organizational role description
The user's display name in this organization
User profile picture encoded as base64
The display language to use (e.g. en, de) - defaults to browser settings
en
True if the user is active in this organization - can be false if removed but not deleted
True if the user has not yet confirmed an invite
Other user-profile related settings, e.g. theme
{}
meta
object
required
{
"data": [
{
"id": 0,
"is_deleted": true,
"created_at": "1970-01-01T00:00:00.000Z",
"created_by": 0,
"modified_at": "1970-01-01T00:00:00.000Z",
"modified_by": 0,
"deleted_at": "1970-01-01T00:00:00.000Z",
"deleted_by": 0,
"_etag": "string",
"user_id": 0,
"email": "string",
"job_title": "",
"display_name": "string",
"picture_data": "",
"display_language": "en",
"is_active": true,
"is_invite_pending": true,
"data": {}
}
],
"meta": {
"count": 0,
"limit": 0,
"offset": 0,
"totalCount": 0
}
}
The request failed because invalid request parameters or data were supplied or access was denied.
- application/json
- Schema
- Example (from schema)
Schema
The error code describing the general error category.
API_INVALID_INPUT_DATA
The HTTP status code.
The actual error message describing the error in more detail.
The request id for following up on specific errors.
{
"code": "API_INVALID_INPUT_DATA",
"status": 0,
"message": "string",
"reqid": "string"
}
The request failed because an error occurred during processing of the request.
- application/json
- Schema
- Example (from schema)
Schema
The error code describing the general error category.
API_INVALID_INPUT_DATA
The HTTP status code.
The actual error message describing the error in more detail.
The request id for following up on specific errors.
{
"code": "API_INVALID_INPUT_DATA",
"status": 0,
"message": "string",
"reqid": "string"
}