All Verbs | /mynotif |
---|
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
Userid | query | int | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
Success | form | bool | No | |
myNotif | form | List<MyNotifView> | No | |
Mycount | form | int | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
NotifId | form | int | No | |
Userid | form | int | No | |
Status | form | string | No | |
Title | form | string | No | |
Types | form | string | No | |
Icons | form | string | No | |
Subtitle | form | string | No | |
Createdate | 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 /mynotif HTTP/1.1
Host: service.cemberle.com
Accept: text/jsv
Content-Type: text/jsv
Content-Length: length
{
userid: 0
}
HTTP/1.1 200 OK Content-Type: text/jsv Content-Length: length { success: False, myNotif: [ { notifId: 0, userid: 0, status: String, title: String, types: String, icons: String, subtitle: String, createdate: 0001-01-01 } ], mycount: 0 }