| PUT | /POS/UM/Users/{UserID} | ||
|---|---|---|---|
| PUT | /POS/UM/Users/ |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| UserID | path | int | No | |
| UserName | body | string | No | |
| Password | body | string | No | |
| FirstName | body | string | No | |
| LastName | body | string | No | |
| Spend | body | bool | No | |
| CardID | body | string | No | |
| body | string | No | ||
| Note | body | string | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| ResponseStatus | form | ResponseStatus | No | |
| Result | form | bool | No | |
| UserID | 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 /POS/UM/Users/{UserID} HTTP/1.1
Host: 10.10.0.107
Accept: application/json
Content-Type: application/json
Content-Length: length
{"UserID":0,"UserName":"String","Password":"String","FirstName":"String","LastName":"String","Spend":false,"CardID":"String","Email":"String","Note":"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"}},"Result":false,"UserID":0}