<back to all web services
RolesUser
The following routes are available for this service:GET | /roles/{UserId} | Retrieve Roles cor given User | |
---|
PUT | /roles/{UserId} | Update the Roles for given User | |
---|
RolesUser Parameters:Name | Parameter | Data Type | Required | Description |
---|
roles | body | List<Roles> | No | |
UserId | path | Guid | No | |
Roles Parameters:Name | Parameter | Data Type | Required | Description |
---|
roles | form | List<Roles> | No | |
UserId | form | Guid | No | |
To override the Content-type in your clients, use the HTTP Accept Header, append the .xml suffix or ?format=xml
HTTP + XML
The following are sample HTTP requests and responses.
The placeholders shown need to be replaced with actual values.
PUT /roles/{UserId} HTTP/1.1
Host: n3tapi.palmettovdc.com
Accept: application/xml
Content-Type: application/xml
Content-Length: length
<RolesUser xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/N3TAPI.Services.DTO">
<UserId>00000000-0000-0000-0000-000000000000</UserId>
<roles xmlns:d2p1="http://schemas.datacontract.org/2004/07/N3TCommon.Entities.N3TLogins.dbo">
<d2p1:Roles>
<Id xmlns="http://schemas.datacontract.org/2004/07/N3TCommon.Entities.N3TLogins">00000000-0000-0000-0000-000000000000</Id>
<d2p1:Role>String</d2p1:Role>
<d2p1:RoleDescription>String</d2p1:RoleDescription>
<d2p1:RoleId>String</d2p1:RoleId>
</d2p1:Roles>
</roles>
</RolesUser>