| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| devicelist | query | List<device> | No | |
| title | query | string | No | |
| message | query | string | No | |
| msgcount | query | int | No | |
| level | query | string | No | |
| validyn | query | string | No | |
| eblastyn | query | string | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| form | string | No | ||
| devicetoken | form | string | No | |
| iosyn | form | string | No |
To override the Content-type in your clients, use the HTTP Accept Header, append the .soap11 suffix or ?format=soap11
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
POST /soap11 HTTP/1.1
Host: ssl.buildersaccess.com
Content-Type: text/xml; charset=utf-8
Content-Length: length
SOAPAction: ba_pushnotificationlistWin
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<ba_pushnotificationlistWin xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/BASchedulingSDK">
<devicelist>
<device>
<devicetoken>String</devicetoken>
<email>String</email>
<iosyn>String</iosyn>
</device>
</devicelist>
<eblastyn>String</eblastyn>
<level>String</level>
<message>String</message>
<msgcount>0</msgcount>
<title>String</title>
<validyn>String</validyn>
</ba_pushnotificationlistWin>
</soap:Body>
</soap:Envelope>