| GET | /POS/UM/Users/ |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| ResponseStatus | form | ResponseStatus | No | |
| Result | form | List<POSUsers_DTO> | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| UserId | form | int | No | |
| UserName | form | string | No | |
| PasswordHash | form | string | No | |
| PasswordSalt | form | string | No | |
| Spend | form | bool | No | |
| FirstName | form | string | No | |
| LastName | form | string | No | |
| CardID | form | string | No | |
| form | string | No | ||
| Note | form | string | No |
To override the Content-type in your clients, use the HTTP Accept Header, append the .jsv suffix or ?format=jsv
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
GET /POS/UM/Users/ HTTP/1.1 Host: 10.10.0.107 Accept: text/jsv
HTTP/1.1 200 OK
Content-Type: text/jsv
Content-Length: length
{
ResponseStatus:
{
ErrorCode: String,
Message: String,
StackTrace: String,
Errors:
[
{
ErrorCode: String,
FieldName: String,
Message: String,
Meta:
{
String: String
}
}
],
Meta:
{
String: String
}
},
Result:
[
{
UserId: 0,
UserName: String,
PasswordHash: String,
PasswordSalt: String,
Spend: False,
FirstName: String,
LastName: String,
CardID: String,
Email: String,
Note: String
}
]
}