POST | /beneficiary/save |
---|
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
Beneficiaries | body | List<Beneficiary> | No | |
MemberId | body | long | No | |
CreatedBy | body | string | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
Id | form | int | No | |
MemberId | form | int | No | |
Name | form | string | No | |
Birthdate | form | DateTime | No | |
RelationshipToMember | form | string | No | |
IdentificationNumber | form | string | No | |
Allocation | form | int | No |
To override the Content-type in your clients, use the HTTP Accept Header, append the .json suffix or ?format=json
To embed the response in a jsonp callback, append ?callback=myCallback
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
POST /beneficiary/save HTTP/1.1
Host: hcbtas-q-albamfs-api.azurewebsites.net
Accept: application/json
Content-Type: application/json
Content-Length: length
{"beneficiaries":[{"id":0,"memberId":0,"name":"String","birthdate":"0001-01-01T00:00:00.0000000","relationshipToMember":"String","identificationNumber":"String","allocation":0}],"memberId":0,"createdBy":"String"}
HTTP/1.1 200 OK Content-Type: application/json Content-Length: length (HttpWebResponse)