curl --request POST \
--url https://api2.rhombussystems.com/api/user/updateUserSelective \
--header 'Content-Type: application/json' \
--header 'x-auth-apikey: <api-key>' \
--header 'x-auth-scheme: <x-auth-scheme>' \
--data '
{
"bypassSaml": true,
"mfaEnabled": true,
"name": "<string>",
"notificationIntervalsV2": [
{
"activityTriggerMap": {},
"deviceFilterSet": [
"AAAAAAAAAAAAAAAAAAAAAA"
],
"diagnosticTriggerMap": {},
"locationActivityTriggerMap": {},
"locationDiagnosticTriggerMap": {},
"locationFilterSet": [
"AAAAAAAAAAAAAAAAAAAAAA"
],
"locationOnlyFilterSet": [
"AAAAAAAAAAAAAAAAAAAAAA"
],
"minuteOfWeekStart": 123,
"minuteOfWeekStop": 123
}
],
"permissionGroupUuid": "AAAAAAAAAAAAAAAAAAAAAA",
"smsPhoneNumbers": [
"<string>"
],
"summaryEmailEnabled": true,
"userUuid": "AAAAAAAAAAAAAAAAAAAAAA"
}
'{}Selectively updates a user’s details. Omitted fields are ignored but fields with null will unset a value, providing granular control over user updates.
curl --request POST \
--url https://api2.rhombussystems.com/api/user/updateUserSelective \
--header 'Content-Type: application/json' \
--header 'x-auth-apikey: <api-key>' \
--header 'x-auth-scheme: <x-auth-scheme>' \
--data '
{
"bypassSaml": true,
"mfaEnabled": true,
"name": "<string>",
"notificationIntervalsV2": [
{
"activityTriggerMap": {},
"deviceFilterSet": [
"AAAAAAAAAAAAAAAAAAAAAA"
],
"diagnosticTriggerMap": {},
"locationActivityTriggerMap": {},
"locationDiagnosticTriggerMap": {},
"locationFilterSet": [
"AAAAAAAAAAAAAAAAAAAAAA"
],
"locationOnlyFilterSet": [
"AAAAAAAAAAAAAAAAAAAAAA"
],
"minuteOfWeekStart": 123,
"minuteOfWeekStop": 123
}
],
"permissionGroupUuid": "AAAAAAAAAAAAAAAAAAAAAA",
"smsPhoneNumbers": [
"<string>"
],
"summaryEmailEnabled": true,
"userUuid": "AAAAAAAAAAAAAAAAAAAAAA"
}
'{}Documentation Index
Fetch the complete documentation index at: https://api-docs.rhombus.community/llms.txt
Use this file to discover all available pages before exploring further.
Your Rhombus API key. Must be accompanied by the x-auth-scheme header set to api-token (or partner-api-token for partner endpoints).
Authentication scheme identifier. Use api-token for standard API key authentication, partner-api-token for partner API key authentication. Must be paired with the x-auth-apikey header containing your API key.
api-token, api, partner-api-token, partner-api Show child attributes
base 64 (url-safe) uuid string
"AAAAAAAAAAAAAAAAAAAAAA"
base 64 (url-safe) uuid string
"AAAAAAAAAAAAAAAAAAAAAA"
OK
Response object for selective user updates.
Was this page helpful?