| GET | /SalesOrders/{InvoiceID}/Historys/{InvoiceHistoryID}/Lines/{InvoiceLineID}/LineDetails/{DetailsLineID} | Retrieves a sales order line detail. |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| InvoiceID | path | string | No | |
| InvoiceHistoryID | path | string | No | |
| InvoiceLineID | path | string | No | |
| DetailsLineID | path | string | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Cost | form | decimal? | No | |
| DateIn | form | DateTime? | No | |
| ExpiryDate | form | DateTime? | No | |
| SpecialPrice | form | decimal? | No | |
| Quantity | form | decimal? | No | |
| LineDetailID | form | string | No | |
| BinLocation | form | string | No | |
| SerialNo | form | string | No | |
| SOHID | form | string | No | |
| IN_LogicalID | form | string | 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 /SalesOrders/{InvoiceID}/Historys/{InvoiceHistoryID}/Lines/{InvoiceLineID}/LineDetails/{DetailsLineID} HTTP/1.1
Host: api.jiwa.com.au
Accept: application/json
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"Cost":0,"DateIn":"0001-01-01T00:00:00.0000000","ExpiryDate":"0001-01-01T00:00:00.0000000","SpecialPrice":0,"Quantity":0,"LineDetailID":"String","BinLocation":"String","SerialNo":"String","SOHID":"String","IN_LogicalID":"String"}