| GET,POST,PUT,DELETE,OPTIONS | /v1/MaterialType/{MaterialTypeID} | ||
|---|---|---|---|
| GET,POST,PUT,DELETE,OPTIONS | /v1/MaterialType |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| MaterialTypeID | path | int | No | |
| MaterialType | body | List<MaterialType> | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| MaterialTypeID | form | short | No | |
| MaterialTypeName | form | string | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| ResponseStatus | form | ResponseStatus | No | |
| MaterialType | form | List<MaterialType> | 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.
POST /v1/MaterialType/{MaterialTypeID} HTTP/1.1
Host: api.dev.dynamics.trendsic.com
Accept: text/jsv
Content-Type: text/jsv
Content-Length: length
{
MaterialTypeID: 0,
MaterialType:
[
{
MaterialTypeID: 0,
MaterialTypeName: String
}
]
}
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
}
},
MaterialType:
[
{
MaterialTypeID: 0,
MaterialTypeName: String
}
]
}