1. v3
  2. Users
  3. PUT - 3/users/{userid}

Definition

PUT - 3/users/{userId}

Update an existing user in the account.

Required roles: Users (write)

Request information

userId

Type integer
Additional info
Required

Sample: 
{
  "Roles": "sample string 1",
  "Rights": {
    "CreateSurveys": true,
    "LaunchSurveys": true,
    "AnalyzeSurveys": true,
    "AccessAllSurveys": true,
    "AccessAllContactLists": true,
    "ManageContacts": true,
    "DistributeSMS": true,
    "DistributePanels": true,
    "ManageThemes": true,
    "EditAppearance": true,
    "ManageNotifications": true,
    "ManageMedia": true
  },
  "SurveyList": "sample string 2"
}
Sample: 
<UpdateUserPermissionsRequest xmlns:i="http://www.w3.org/2001/XMLSchema-instance">
  <Rights>
    <AccessAllContactLists>true</AccessAllContactLists>
    <AccessAllSurveys>true</AccessAllSurveys>
    <AnalyzeSurveys>true</AnalyzeSurveys>
    <CreateSurveys>true</CreateSurveys>
    <DistributePanels>true</DistributePanels>
    <DistributeSMS>true</DistributeSMS>
    <EditAppearance>true</EditAppearance>
    <LaunchSurveys>true</LaunchSurveys>
    <ManageContacts>true</ManageContacts>
    <ManageMedia>true</ManageMedia>
    <ManageNotifications>true</ManageNotifications>
    <ManageThemes>true</ManageThemes>
  </Rights>
  <Roles>sample string 1</Roles>
  <SurveyList>sample string 2</SurveyList>
</UpdateUserPermissionsRequest>

Response information


Meta

The metadata such as paging parameters, status code, timestamp,... which are related to this request.


Type MetaData
Data

The actual data returned by the request.


Type UpdateUserResponse
Links

HATEOAS related to this object. It wil contain relevant url's such as previous and next page for paged results, create/update/delete action. These url's can be used in your application for the next steps in your application logic.


Type Hateoas

Note about API metadata
The API uses the same metadata structure for all endpoints, but not every field applies to every endpoint. Fields such as paging details (for example Limit, Offset and TotalRowCount) and IsFiltered are only returned by endpoints that support them. Fields that do not apply are not included in the actual response.
Sample: 
{
  "Meta": {
    "Status": 1,
    "TotalRowCount": 1,
    "Limit": 1,
    "Offset": 1,
    "TotalPageCount": 1,
    "StartRec": 1,
    "StopRec": 1,
    "Timestamp": "2026-11-13T20:04:48.2353778Z",
    "IsFiltered": true
  },
  "Data": {
    "Success": true,
    "UserNotFound": true
  }
}
Sample: 
<Payload xmlns:i="http://www.w3.org/2001/XMLSchema-instance" z:Id="i1" xmlns:z="http://schemas.microsoft.com/2003/10/Serialization/">
  <Data>
    <Success>true</Success>
    <UserNotFound>true</UserNotFound>
  </Data>
  <Meta>
    <IsFiltered>true</IsFiltered>
    <Limit>1</Limit>
    <Offset>1</Offset>
    <StartRec>1</StartRec>
    <Status>1</Status>
    <StopRec>1</StopRec>
    <Timestamp>2026-11-13T20:04:48.2353778+00:00</Timestamp>
    <TotalPageCount>1</TotalPageCount>
    <TotalRowCount>1</TotalRowCount>
  </Meta>
</Payload>