POST | /members/contactus |
---|
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
Subject | body | string | No | |
EmailMember | body | string | No | |
Text | body | string | No | |
SendToCc | body | string | No | |
SendReplyTo | body | string | No | |
SendToBCC | body | string | No | |
SendFrom | body | string | No | |
UserToken | body | string | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
HomeUrl | form | string | No | |
Success | form | bool | No | |
IsPensionSight | form | bool | 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 /members/contactus HTTP/1.1
Host: hcbtas-q-albamfs-api.azurewebsites.net
Accept: application/json
Content-Type: application/json
Content-Length: length
{"subject":"String","emailMember":"String","text":"String","sendToCc":"String","sendReplyTo":"String","sendToBCC":"String","sendFrom":"String","userToken":"String"}
HTTP/1.1 200 OK Content-Type: application/json Content-Length: length {"homeUrl":"String","success":false,"isPensionSight":false}