| POST | /Support/{TicketRef} |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| SupportTicketResponseID | form | int | No | |
| SupportTicketID | form | int | No | |
| ResponseBy | form | string | No | |
| AdminID | form | int | No | |
| Message | form | string | No | |
| DateCreated | form | DateTime | No | |
| IsAdminView | form | bool | No | |
| DateDeleted | form | DateTime? | No | |
| DeletedBy | 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 /Support/{TicketRef} HTTP/1.1
Host: tstsrvs.redhotpie.com.au
Accept: application/json
Content-Type: application/json
Content-Length: length
{"TicketRef":"String","Message":"String","Attachments":[0],"UserAgent":"String"}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"SupportTicketResponseID":0,"SupportTicketID":0,"ResponseBy":"String","AdminID":0,"Message":"String","DateCreated":"\/Date(-62135596800000-0000)\/","IsAdminView":false,"DateDeleted":"\/Date(-62135596800000-0000)\/","DeletedBy":0}