| POST | /Warehousing/LogisticsSchedule |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Schedule | body | LogisticsSchedule | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| ScheduleID | form | int | No | |
| ScheduleType | form | short | No | |
| ScheduleDateSt | form | DateTime? | No | |
| ScheduleDateEn | form | DateTime? | No | |
| ScheduleString | form | string | No | |
| MinDeliveryTime | form | DateTime? | No | |
| MaxDeliveryTime | form | DateTime? | No | |
| DeliveryDayAdd | form | byte | No | |
| br | form | int? | No | |
| Acc | form | string | No | |
| Spend | form | bool | No | |
| Acc_nu | form | string | No | |
| Brname | form | string | No | |
| cUser | form | string | No | |
| Comment | form | string | No | |
| category_id | form | string | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| ResponseStatus | form | ResponseStatus | No | |
| NewScheduleId | form | int? | 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.
POST /Warehousing/LogisticsSchedule HTTP/1.1
Host: 10.10.0.107
Accept: text/jsv
Content-Type: text/jsv
Content-Length: length
{
Schedule:
{
ScheduleID: 0,
ScheduleType: 0,
ScheduleDateSt: 0001-01-01,
ScheduleDateEn: 0001-01-01,
ScheduleString: String,
MinDeliveryTime: 0001-01-01,
MaxDeliveryTime: 0001-01-01,
DeliveryDayAdd: 0,
br: 0,
Acc: String,
Spend: False,
Acc_nu: String,
Brname: String,
cUser: String,
Comment: String,
category_id: String
}
}
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
}
},
NewScheduleId: 0
}