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