regis

UserRoleUpdateRequest

**Requires Authentication**
Required role:	REGISUserRole

The following routes are available for this service:
POST	/UserRoles/{uuid}/Update

**UserRoleUpdateRequest** Parameters:
Name	Parameter	Data Type	Required
uuid	path	string	No
authorizing_uuid	body	string	No
admin_auth_secret	body	string	No
is_staff	body	bool	No
role_ids	body	List<int>	No

**UserRoleResponse** Parameters:
Name	Parameter	Data Type	Required
ResponseStatus	form	ResponseStatus	No
regent_id	form	int	No
uuid	form	string	No
regent_login	form	string	No
first_name	form	string	No
last_name	form	string	No
email	form	string	No
is_staff	form	bool	No
roles	form	List<string>	No

To override the Content-type in your clients, use the HTTP Accept Header, append the .other suffix or ?format=other

HTTP + OTHER

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

POST /UserRoles/{uuid}/Update HTTP/1.1 
Host: data.regent-college.edu 
Accept: text/jsonl
Content-Type: text/jsonl
Content-Length: length

{"uuid":"String","authorizing_uuid":"String","admin_auth_secret":"String","is_staff":false,"role_ids":[0]}

HTTP/1.1 200 OK
Content-Type: text/jsonl
Content-Length: length

{"responseStatus":{"errorCode":"String","message":"String","stackTrace":"String","errors":[{"errorCode":"String","fieldName":"String","message":"String","meta":{"String":"String"}}],"meta":{"String":"String"}},"regent_id":0,"uuid":"String","regent_login":"String","first_name":"String","last_name":"String","email":"String","is_staff":false,"roles":["String"]}