| All Verbs | /ba_submitphotovendor |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| token | query | string | Yes | |
| tokensecret | query | string | Yes | |
| idvendor | query | string | Yes | |
| idwebcare1 | query | string | Yes | |
| idwebcare1detail | query | string | Yes | |
| photo | query | string | Yes | |
| xtag | query | string | Yes | |
| creaby | query | string | No | |
| photoTime | query | string | No | |
| photoTaker | query | string | No | |
| photoLat | query | string | No | |
| photoLng | 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/ba_submitphotovendor HTTP/1.1
Host: ssl.buildersaccess.com
Content-Type: application/xml
Content-Length: length
<ba_submitphotovendor xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/BASchedulingSDK">
<creaby>String</creaby>
<idvendor>String</idvendor>
<idwebcare1>String</idwebcare1>
<idwebcare1detail>String</idwebcare1detail>
<photo>String</photo>
<photoLat>String</photoLat>
<photoLng>String</photoLng>
<photoTaker>String</photoTaker>
<photoTime>String</photoTime>
<token>String</token>
<tokensecret>String</tokensecret>
<xtag>String</xtag>
</ba_submitphotovendor>