| GET | /Warehousing/GroupRange/{RangId} | ||
|---|---|---|---|
| GET | /Warehousing/GroupRange |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| RangId | path | int? | No | |
| Full | query | bool | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| ResponseStatus | form | ResponseStatus | No | |
| Result | form | List<GroupRange> | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| RangdId | form | int | No | |
| StartCount | form | decimal | No | |
| EndCount | form | decimal? | No | |
| DisCount | form | decimal | No | |
| RangId | form | int? | No | |
| RangeName | form | string | No | |
| RangType | form | bool | 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 /Warehousing/GroupRange/{RangId} 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:
[
{
RangdId: 0,
StartCount: 0,
EndCount: 0,
DisCount: 0,
RangId: 0,
RangeName: String,
RangType: False
}
]
}