| PUT | /products_harvests/{Id} |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Id | path | long | Yes | |
| TenantsId | body | long | Yes | |
| ZonesId | body | long | Yes | |
| ProductsId | body | long | Yes | |
| HarvestDescription | body | string | Yes | |
| Quarters | body | int | Yes | |
| QtyG | body | int | Yes | |
| Final | body | bool | Yes |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Id | form | long | No | |
| TenantsId | form | long | No | |
| ZonesId | form | long | No | |
| ProductsId | form | long | No | |
| HarvestDescription | form | string | No | |
| Quarters | form | int | No | |
| QtyG | form | int | No | |
| Final | form | bool | No | |
| ResponseStatus | form | ResponseStatus | 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.
PUT /products_harvests/{Id} HTTP/1.1
Host: api.sfgtec.com
Accept: application/json
Content-Type: application/json
Content-Length: length
{"id":0,"tenantsId":0,"zonesId":0,"productsId":0,"harvestDescription":"String","quarters":0,"qtyG":0,"final":false}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"id":0,"tenantsId":0,"zonesId":0,"productsId":0,"harvestDescription":"String","quarters":0,"qtyG":0,"final":false,"responseStatus":{"errorCode":"String","message":"String","stackTrace":"String","errors":[{"errorCode":"String","fieldName":"String","message":"String","meta":{"String":"String"}}],"meta":{"String":"String"}}}