| GET | /LoyaltyCards/DcFamily | ||
|---|---|---|---|
| GET | /LoyaltyCards/Persons/Family | ||
| GET | /LoyaltyCards/Persons/{UnID}{/Family |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| UnID | query | Guid? | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| ResponseStatus | form | ResponseStatus | No | |
| Result | form | List<DcFamily> | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| FamilyID | form | int | No | |
| UnID | form | Guid | No | |
| TypeID | form | int | No | |
| FName | form | string | No | |
| BDate | form | DateTime? | No | |
| Note | form | string | No | |
| HName | form | string | 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 /LoyaltyCards/DcFamily 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:
[
{
FamilyID: 0,
UnID: 00000000000000000000000000000000,
TypeID: 0,
FName: String,
BDate: 0001-01-01,
Note: String,
HName: String
}
]
}