| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| code | query | string | No | |
| subcontractorSign | query | string | No | |
| subcontractorPrintedName | query | string | No | |
| subcontractor2Sign | query | string | No | |
| EstimatedNumberOfEmployeesAffected | query | string | No | |
| Subcontractor3Sign | 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_submit_masterAgreement_forWeb
<?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_submit_masterAgreement_forWeb xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/BASchedulingSDK">
<EstimatedNumberOfEmployeesAffected>String</EstimatedNumberOfEmployeesAffected>
<Subcontractor3Sign>String</Subcontractor3Sign>
<code>String</code>
<subcontractor2Sign>String</subcontractor2Sign>
<subcontractorPrintedName>String</subcontractorPrintedName>
<subcontractorSign>String</subcontractorSign>
</sch_submit_masterAgreement_forWeb>
</soap:Body>
</soap:Envelope>
HTTP/1.1 200 OK Content-Type: application/xml Content-Length: length (string)