| GET | /Shipments/{ShipmentID}/PurchaseOrders/{OrderID} | Retrieves a shipment purchase order. |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| ShipmentID | path | string | No | |
| OrderID | path | string | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| PurchaseOrderReceivedID | form | string | No | |
| OrderID | form | string | No | |
| OrderNo | form | string | No | |
| OrderedDate | form | DateTime? | No | |
| ItemNo | form | int? | No | |
| UserField1 | form | string | No | |
| UserField2 | form | string | No | |
| UserField3 | form | string | No | |
| UserField4 | form | string | No | |
| UserField5 | form | string | No | |
| UserField6 | form | string | No | |
| UserField7 | form | string | No | |
| UserField8 | form | string | No | |
| UserField9 | form | string | No | |
| UserField10 | 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 /Shipments/{ShipmentID}/PurchaseOrders/{OrderID} HTTP/1.1
Host: localhost
Accept: application/json
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"PurchaseOrderReceivedID":"String","OrderID":"String","OrderNo":"String","OrderedDate":"0001-01-01T00:00:00.0000000","ItemNo":0,"UserField1":"String","UserField2":"String","UserField3":"String","UserField4":"String","UserField5":"String","UserField6":"String","UserField7":"String","UserField8":"String","UserField9":"String","UserField10":"String"}