| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| token | query | string | No | |
| tokensecret | query | string | No | |
| xidcia | query | string | No | |
| idpo | query | string | No | |
| xtype | query | string | No | |
| oldvendoremail | query | string | No | |
| msg | query | string | No | |
| EquipmentType | query | 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: sch_pmPOSendMessage
<?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>
<sch_pmPOSendMessage xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/BASchedulingSDK">
<EquipmentType>String</EquipmentType>
<idpo>String</idpo>
<msg>String</msg>
<oldvendoremail>String</oldvendoremail>
<token>String</token>
<tokensecret>String</tokensecret>
<xidcia>String</xidcia>
<xtype>String</xtype>
</sch_pmPOSendMessage>
</soap:Body>
</soap:Envelope>