| All Verbs | /sch_submitchecklist |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| token | query | string | No | |
| tokensecret | query | string | No | |
| taskid | query | string | No | |
| vendorcontact | query | string | No | |
| comment | query | string | No | |
| listcheck | query | List<Sch_CheckData> | No | |
| latitude | query | decimal | No | |
| longitude | query | decimal | 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_submitchecklist HTTP/1.1
Host: ssl.buildersaccess.com
Content-Type: application/xml
Content-Length: length
<sch_submitchecklist xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/BASchedulingSDK">
<comment>String</comment>
<latitude>0</latitude>
<listcheck>
<AppResponse.Sch_CheckData>
<_x003C_checkedyn_x003E_k__BackingField>false</_x003C_checkedyn_x003E_k__BackingField>
<_x003C_description_x003E_k__BackingField>String</_x003C_description_x003E_k__BackingField>
<_x003C_idcomment2_x003E_k__BackingField>String</_x003C_idcomment2_x003E_k__BackingField>
<_x003C_item_x003E_k__BackingField>String</_x003C_item_x003E_k__BackingField>
</AppResponse.Sch_CheckData>
</listcheck>
<longitude>0</longitude>
<taskid>String</taskid>
<token>String</token>
<tokensecret>String</tokensecret>
<vendorcontact>String</vendorcontact>
</sch_submitchecklist>