POST | /api/users/{UserGuid}/roles/{RoleGuid} | Assign role to user | |
---|---|---|---|
DELETE | /api/users/{UserGuid}/roles/{RoleGuid} | Unassign role to user |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
UserGuid | path | Guid | Yes | |
RoleGuid | path | Guid | Yes |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
ResponseStatus | form | ResponseStatus | No |
To override the Content-type in your clients, use the HTTP Accept Header, append the .json suffix or ?format=json
To embed the response in a jsonp callback, append ?callback=myCallback
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
POST /api/users/{UserGuid}/roles/{RoleGuid} HTTP/1.1
Host: api.secure-messaging.com
Accept: application/json
Content-Type: application/json
Content-Length: length
{
"userGuid": "00000000000000000000000000000000",
"roleGuid": "00000000000000000000000000000000"
}
HTTP/1.1 200 OK Content-Type: application/json Content-Length: length { "responseStatus": { "errorCode": "String", "message": "String", "stackTrace": "String", "errors": [ { "errorCode": "String", "fieldName": "String", "message": "String", "meta": { "String": "String" } } ], "meta": { "String": "String" } } }