| GET | /User/Account/ |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| UserID | form | long | No | |
| Username | form | string | No | |
| EmailAddress | form | string | No | |
| Verified | form | bool | No | |
| RegisteredOn | form | DateTime | No | |
| XMPPPassword | 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.
GET /User/Account/ HTTP/1.1 Host: tstsrvs.redhotpie.com.au Accept: application/json
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"UserID":0,"Username":"String","EmailAddress":"String","Verified":false,"RegisteredOn":"\/Date(-62135596800000-0000)\/","XMPPPassword":"String"}