| GET | /Manufacturing/Tara/ByCode/{Code} | ||
|---|---|---|---|
| GET | /Manufacturing/Tara | ||
| GET | /Manufacturing/Tara/{ID} |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| ID | path | int? | No | |
| Code | path | string | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| ResponseStatus | form | ResponseStatus | No | |
| Result | form | List<ManufactureTara> | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| TaraID | form | int | No | |
| Code | form | string | No | |
| Name | form | string | No | |
| TaraType | form | int | No | |
| Weight | form | decimal? | No | |
| LocationID | 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 /Manufacturing/Tara/ByCode/{Code} 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
}
},
Result:
[
{
TaraID: 0,
Code: String,
Name: String,
TaraType: 0,
Weight: 0,
LocationID: 0
}
]
}