| All Verbs | /lookups/productInstances |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Id | form | string | No | |
| Data | form | List<ProductInstanceRef> | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Id | form | string | No | |
| Name | form | string | No | |
| Product | form | ProductReference | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Id | form | string | No | |
| Value | form | string | No | |
| Category | form | string | No | |
| ProductProvider | form | Reference | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Id | form | string | No | |
| Value | 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.
POST /lookups/productInstances HTTP/1.1
Host: api.wwin.ath.cx
Accept: application/json
Content-Type: application/json
Content-Length: length
{}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"id":"String","data":[{"id":"String","name":"String","product":{"id":"String","value":"String","category":"String","productProvider":{"id":"String","value":"String"}}}]}