All Verbs | /post_pm_notificationList |
---|
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
token | query | string | Yes | |
tokensecret | query | string | Yes | |
query | string | Yes |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
notifications | form | List<post_notifications> | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
result | form | int | No | |
message | form | string | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
idnumber | form | long | No | |
idtenant1 | form | int | No | |
message | form | string | No | |
related_table | form | string | No | |
related_tableID | form | long | No | |
read_yn | form | bool | No | |
read_date | form | DateTime | No | |
read_by | form | string | No | |
creadate | form | DateTime | No |
To override the Content-type in your clients, use the HTTP Accept Header, append the .jsv suffix or ?format=jsv
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
POST /jsv/reply/post_pm_notificationList HTTP/1.1
Host: sdk.lovettcommercial.com
Content-Type: text/jsv
Content-Length: length
{
token: String,
tokensecret: String,
email: String
}
HTTP/1.1 200 OK Content-Type: text/jsv Content-Length: length { notifications: [ { idnumber: 0, idtenant1: 0, message: String, related_table: String, related_tableID: 0, read_yn: False, read_date: 0001-01-01, read_by: String, creadate: 0001-01-01 } ], result: 0, message: String }