| GET | /Accounting/FixedAsets/Supp/Det/PersonsHistory |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| SuppDetId | query | int | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| ResponseStatus | form | ResponseStatus | No | |
| Result | form | List<SuppDetPersonsHistory> | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| sdate | form | DateTime | No | |
| edate | form | DateTime? | No | |
| lsort | form | int | No | |
| cuser | form | string | No | |
| crtime | form | DateTime? | No | |
| lvalue | form | int? | No | |
| note | form | string | No | |
| pernum | form | string | No | |
| pname | 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 /Accounting/FixedAsets/Supp/Det/PersonsHistory 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:
[
{
sdate: 0001-01-01,
edate: 0001-01-01,
lsort: 0,
cuser: String,
crtime: 0001-01-01,
lvalue: 0,
note: String,
pernum: String,
pname: String
}
]
}