POST | /News_AvailableNotifications |
---|
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
Id | form | long | No | |
ContactTeam | form | string | No | |
CreateDate | form | DateTime | No |
To override the Content-type in your clients, use the HTTP Accept Header, append the .xml suffix or ?format=xml
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
POST /News_AvailableNotifications HTTP/1.1
Host: wbs.e-teleport.ru
Accept: application/xml
Content-Type: application/xml
Content-Length: length
<News_AvailableNotifications xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TeleportService.ServiceModel" />
HTTP/1.1 200 OK Content-Type: application/xml Content-Length: length <NewsAvailableNotificationsResponce xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TeleportService.ServiceModel"> <ContactTeam>String</ContactTeam> <CreateDate>0001-01-01T00:00:00</CreateDate> <Id>0</Id> </NewsAvailableNotificationsResponce>