| Requires any of the permissions: | create-role, edit-role |
| POST | /roles |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Id | body | int | No | |
| RoleName | body | string | Yes | |
| RoleCode | body | string | Yes | |
| IsActive | body | byte | No | |
| Permissions | body | string[] | Yes |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Code | form | int | No | |
| Message | form | string | No | |
| Data | form | SystemConfig | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Id | form | int | No | |
| Name | form | string | Yes | |
| Value | form | string | Yes | |
| Description | form | string | Yes | |
| IsActive | form | bool | No | |
| CreatedDate | form | DateTime | Yes | |
| UpdatedDate | form | DateTime | Yes |
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 /roles HTTP/1.1
Host: chienbinhdevias-admin-api-sandbox.adnx.vn
Accept: application/json
Content-Type: application/json
Content-Length: length
{"id":0,"roleName":"String","roleCode":"String","isActive":0,"permissions":["String"]}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"code":0,"message":"String","data":{"id":0,"roleName":"String","roleCode":"String","description":"String","showPermission":"String","isActive":0,"status":0,"createdDate":"0001-01-01T00:00:00.0000000+07:06","updatedDate":"0001-01-01T00:00:00.0000000+07:06"}}