| All Verbs | /sch_vendorSignAgreement |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| token | query | string | No | |
| tokensecret | query | string | No | |
| idcia | query | string | No | |
| idvendor | query | string | No | |
| vendor_email | query | string | No | |
| subcontractor | query | string | No | |
| printed_name | query | string | No | |
| subcontractor_address | query | string | No | |
| subcontractor_signature | query | string | No | |
| isSignWithAmericanIntown | 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_vendorSignAgreement HTTP/1.1
Host: ssl.buildersaccess.com
Content-Type: application/xml
Content-Length: length
<sch_vendorSignAgreement xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/BASchedulingSDK">
<idcia>String</idcia>
<idvendor>String</idvendor>
<isSignWithAmericanIntown>String</isSignWithAmericanIntown>
<printed_name>String</printed_name>
<subcontractor>String</subcontractor>
<subcontractor_address>String</subcontractor_address>
<subcontractor_signature>String</subcontractor_signature>
<token>String</token>
<tokensecret>String</tokensecret>
<vendor_email>String</vendor_email>
</sch_vendorSignAgreement>