| All Verbs | /SearchProperty_v23 |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| token | query | string | Yes | |
| tokensecret | query | string | Yes | |
| mastercompany | query | string | Yes | |
| query | string | Yes | ||
| keyword | query | string | Yes | |
| idcia | query | string | Yes | |
| idproject | query | string | Yes |
To override the Content-type in your clients, use the HTTP Accept Header, append the .jsv suffix or ?format=jsv
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
POST /jsv/reply/SearchProperty_v23 HTTP/1.1
Host: app.lovettcommercial.com
Content-Type: text/jsv
Content-Length: length
{
token: String,
tokensecret: String,
mastercompany: String,
email: String,
keyword: String,
idcia: String,
idproject: String
}
HTTP/1.1 200 OK
Content-Type: text/jsv
Content-Length: length
{
validtoken: String,
found: String,
existyn: String,
listProperty:
[
{
fs: String,
chat: String,
namecity: String,
ciaid: String,
cianame: String,
ledger: String,
idnumber: String,
name: String,
proptype: String,
proptype2: String,
insdate: String,
liability: String,
building: String,
insurance_premium: String,
property_coverage: String,
status: String,
recordationdate: String,
lotsize: String,
bldgsf: String,
leasedsf: String,
vacantsf: String,
nsuite: String,
ntenant: String,
npsf: String,
checkInOut:
[
{
idnumber: String,
idcia: String,
idproject: String,
latitude: String,
longitude: String,
checkin_date: String,
notes: String,
circle_status: String,
distance: String,
employeeemail: String,
employeecontact: String,
checkType: String
}
]
}
]
}