Tenant Server V1

post_propertylist

The following routes are available for this service:
All Verbs	/post_propertylist

**post_propertylist** Parameters:
Name	Parameter	Data Type	Required
token	query	string	Yes
tokensecret	query	string	Yes
email	query	string	Yes
keywords	query	string	No

**post_propertylistResponse** Parameters:
Name	Parameter	Data Type	Required
result	form	int	No
message	form	string	No
list	form	List<propertyInfo>	No

**propertyInfo** Parameters:
Name	Parameter	Data Type	Required
idproject	form	string	No
idcia	form	string	No
name	form	string	No
address	form	string	No
city	form	string	No
zipcode	form	string	No

To override the Content-type in your clients, use the HTTP Accept Header, append the .xml suffix or ?format=xml

HTTP + XML

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

POST /xml/reply/post_propertylist HTTP/1.1 
Host: sdk.lovettcommercial.com 
Content-Type: application/xml
Content-Length: length

<post_propertylist xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TenantSDK.post.Request">
  <email>String</email>
  <keywords>String</keywords>
  <token>String</token>
  <tokensecret>String</tokensecret>
</post_propertylist>

HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length

<post_propertylistResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TenantSDK.post.Request">
  <list>
    <propertyInfo>
      <address>String</address>
      <city>String</city>
      <idcia>String</idcia>
      <idproject>String</idproject>
      <name>String</name>
      <zipcode>String</zipcode>
    </propertyInfo>
  </list>
  <message>String</message>
  <result>0</result>
</post_propertylistResponse>