| GET | /RS/Spec/MofApexSpecProducts |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| ResponseStatus | form | ResponseStatus | No | |
| MofApexSpecProducts | form | List<MofApexSpecProducts> | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| ID | form | int? | No | |
| MofProdSSFCode | form | string | No | |
| MofProdName | form | string | No | |
| MofProdSSNCode | form | string | No | |
| prodpp_id | form | string | No | |
| ProdName | form | string | No | |
| BCode | form | string | No | |
| MofProdId | form | int? | No |
To override the Content-type in your clients, use the HTTP Accept Header, append the .jsv suffix or ?format=jsv
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
GET /RS/Spec/MofApexSpecProducts HTTP/1.1 Host: 10.10.0.107 Accept: text/jsv
HTTP/1.1 200 OK
Content-Type: text/jsv
Content-Length: length
{
ResponseStatus:
{
ErrorCode: String,
Message: String,
StackTrace: String,
Errors:
[
{
ErrorCode: String,
FieldName: String,
Message: String,
Meta:
{
String: String
}
}
],
Meta:
{
String: String
}
},
MofApexSpecProducts:
[
{
ID: 0,
MofProdSSFCode: String,
MofProdName: String,
MofProdSSNCode: String,
prodpp_id: String,
ProdName: String,
BCode: String,
MofProdId: 0
}
]
}