| PUT | /Manufacturing/Roles |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| RoleId | body | int | No | |
| Name | body | string | No | |
| NameEn | body | string | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| ResponseStatus | form | ResponseStatus | No | |
| RoleId | form | int? | 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.
PUT /Manufacturing/Roles HTTP/1.1
Host: 10.10.0.107
Accept: application/json
Content-Type: application/json
Content-Length: length
{"RoleId":0,"Name":"String","NameEn":"String"}
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"}},"RoleId":0}