| GET | /Common/Dictionary/ProducingExpMDetails |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Acc | query | string | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| ResponseStatus | form | ResponseStatus | No | |
| Result | form | List<ProducingExpMDetails> | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| expid | form | int | No | |
| Acc1 | form | string | No | |
| Acc2 | form | string | No | |
| Name | 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 /Common/Dictionary/ProducingExpMDetails HTTP/1.1 Host: 10.10.0.107 Accept: application/json
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"ResponseStatus":{"ErrorCode":"String","Message":"String","StackTrace":"String","Errors":[{"ErrorCode":"String","FieldName":"String","Message":"String","Meta":{"String":"String"}}],"Meta":{"String":"String"}},"Result":[{"expid":0,"Acc1":"String","Acc2":"String","Name":"String"}]}