| All Verbs | /sch_pushnotification |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| token | query | string | No | |
| tokensecret | query | string | No | |
| message | query | string | No | |
| title | query | string | No | |
| taskid | query | string | No | |
| idcia | query | string | No | |
| idpo1 | query | string | No | |
| listemail | query | List<string> | No | |
| validyn | query | string | No | |
| eblastyn | query | string | No | |
| idvendor | query | string | No | |
| frompmyn | query | string | 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 /xml/oneway/sch_pushnotification HTTP/1.1
Host: ssl.buildersaccess.com
Content-Type: application/xml
Content-Length: length
<sch_pushnotification xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/BASchedulingSDK">
<eblastyn>String</eblastyn>
<frompmyn>String</frompmyn>
<idcia>String</idcia>
<idpo1>String</idpo1>
<idvendor>String</idvendor>
<listemail xmlns:d2p1="http://schemas.microsoft.com/2003/10/Serialization/Arrays">
<d2p1:string>String</d2p1:string>
</listemail>
<message>String</message>
<taskid>String</taskid>
<title>String</title>
<token>String</token>
<tokensecret>String</tokensecret>
<validyn>String</validyn>
</sch_pushnotification>