| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| token | query | string | No | |
| tokensecret | query | string | No | |
| xidcia | query | int | No | |
| idpo1 | query | int | No | |
| idvendor | query | int | No | |
| code | query | long | No | |
| EquipmentType | 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>
<Sch_GetPODetailForSubmit xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/BASchedulingSDK">
<EquipmentType>String</EquipmentType>
<code>0</code>
<idpo1>0</idpo1>
<idvendor>0</idvendor>
<token>String</token>
<tokensecret>String</tokensecret>
<xidcia>0</xidcia>
</Sch_GetPODetailForSubmit>
</soap12:Body>
</soap12:Envelope>