PATCH | /User/Message/Template/{ID} |
---|
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
ID | path | int | No | |
Message | query | string | No | |
Subject | query | string | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
ID | form | int | No | |
UserID | form | long | No | |
Message | form | string | No | |
Subject | form | string | 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.
PATCH /User/Message/Template/{ID} HTTP/1.1
Host: tstsrvs.redhotpie.com.au
Accept: application/json
Content-Type: application/json
Content-Length: length
{"ID":0,"Message":"String","Subject":"String"}
HTTP/1.1 200 OK Content-Type: application/json Content-Length: length {"ID":0,"UserID":0,"Message":"String","Subject":"String"}