All Verbs | /unassignroles |
---|
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
UserName | query | string | No | |
Permissions | query | List<string> | No | |
Roles | query | List<string> | No | |
Meta | query | Dictionary<string, string> | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
AllRoles | form | List<string> | No | |
AllPermissions | form | List<string> | No | |
Meta | form | Dictionary<string, string> | No | |
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 /unassignroles HTTP/1.1
Host: recaudoenee.com
Accept: application/json
Content-Type: application/json
Content-Length: length
{"UserName":"String","Permissions":["String"],"Roles":["String"],"Meta":{"String":"String"}}
HTTP/1.1 200 OK Content-Type: application/json Content-Length: length {"AllRoles":["String"],"AllPermissions":["String"],"Meta":{"String":"String"},"ResponseStatus":{"ErrorCode":"String","Message":"String","StackTrace":"String","Errors":[{"ErrorCode":"String","FieldName":"String","Message":"String","Meta":{"String":"String"}}],"Meta":{"String":"String"}}}