| GET | /Distribution/SalesQuantityPlan/{PlanId} | ||
|---|---|---|---|
| GET | /Distribution/SalesQuantityPlan |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| PlanId | path | int? | No | |
| YearN | query | int | No | |
| MonthN | query | int | No | |
| PresalerId | query | int? | No | |
| ProducerId | query | string | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Result | form | List<SaleQuantityPlan> | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| PlanId | form | int | No | |
| YearN | form | int | No | |
| MonthN | form | int | No | |
| MobileUserId | form | int | No | |
| ProducerId | form | string | No | |
| CategoryId | form | string | No | |
| Quantity | form | decimal | 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.
GET /Distribution/SalesQuantityPlan/{PlanId} HTTP/1.1
Host: 10.10.0.107
Accept: application/json
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"Result":[{"PlanId":0,"YearN":0,"MonthN":0,"MobileUserId":0,"ProducerId":"String","CategoryId":"String","Quantity":0}]}