| GET | /GetTfExpenseByCompany |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| d1 | query | DateTime | No | |
| d2 | query | DateTime | No | |
| companyID | query | int? | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| ResponseStatus | form | ResponseStatus | No | |
| Result | form | List<TfExpenseByCompany> | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| fuel_id | form | int | No | |
| code | form | string | No | |
| fuelname | form | string | No | |
| scount | form | decimal | No | |
| trtype | form | string | No | |
| company_id | form | int | No | |
| rs_code | form | string | No | |
| companyname | 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 /GetTfExpenseByCompany HTTP/1.1 Host: axfuel.apex.ge 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:
[
{
fuel_id: 0,
code: String,
fuelname: String,
scount: 0,
trtype: String,
company_id: 0,
rs_code: String,
companyname: String
}
]
}