All Verbs | /alerts/getbyuser |
---|
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
User | query | string | No | |
Status | query | long? | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
Data | form | List<SystemAlert> | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
Code | form | string | No | |
ErrorMessage | form | string | No | |
ErrorStackTrace | form | string | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
GenerationType | form | long | No | |
GenerationTypeDesc | form | string | No | |
AlertOrigin | form | long | No | |
AlertOriginDesc | form | string | No | |
Message | form | string | No | |
Longitude | form | double | No | |
Latitude | form | double | No | |
ModifiedUser | form | string | No | |
ModifiedDate | form | DateTime | No | |
ModifiedDateDesc | form | string | No | |
Notes | form | string | No | |
Fullinfo | form | string | No | |
Status | form | long | No | |
StatusDesc | 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.
POST /alerts/getbyuser HTTP/1.1
Host: ws.jimsnwa.com
Accept: application/json
Content-Type: application/json
Content-Length: length
{"User":"String","Status":0}
HTTP/1.1 200 OK Content-Type: application/json Content-Length: length {"Data":[{"GenerationType":0,"GenerationTypeDesc":"String","AlertOrigin":0,"AlertOriginDesc":"String","Message":"String","Longitude":0,"Latitude":0,"ModifiedUser":"String","ModifiedDate":"0001-01-01T00:00:00.0000000","ModifiedDateDesc":"String","Notes":"String","Fullinfo":"String","Status":0,"StatusDesc":"String"}],"Code":"String","ErrorMessage":"String","ErrorStackTrace":"String"}