LovettCommercialService V1

Homeowner

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

**Homeowner** Parameters:
Name	Parameter	Data Type	Required
token	query	string	Yes
tokensecret	query	string	Yes
email	query	string	Yes
fname	query	string	Yes
lname	query	string	Yes
phone	query	string	Yes
workphone	query	string	Yes
besttime	query	string	Yes
password	query	string	Yes

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/Homeowner HTTP/1.1 
Host: app.lovettcommercial.com 
Content-Type: application/xml
Content-Length: length

<Homeowner xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/LovettCommercialService">
  <besttime>String</besttime>
  <email>String</email>
  <fname>String</fname>
  <lname>String</lname>
  <password>String</password>
  <phone>String</phone>
  <token>String</token>
  <tokensecret>String</tokensecret>
  <workphone>String</workphone>
</Homeowner>

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

<AppResponse.User xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/LovettCommercialService">
  <_x003C_activeyn_x003E_k__BackingField>false</_x003C_activeyn_x003E_k__BackingField>
  <_x003C_email_x003E_k__BackingField>String</_x003C_email_x003E_k__BackingField>
  <_x003C_existyn_x003E_k__BackingField>String</_x003C_existyn_x003E_k__BackingField>
  <_x003C_found_x003E_k__BackingField>String</_x003C_found_x003E_k__BackingField>
  <_x003C_name_x003E_k__BackingField>String</_x003C_name_x003E_k__BackingField>
  <_x003C_validtoken_x003E_k__BackingField>String</_x003C_validtoken_x003E_k__BackingField>
</AppResponse.User>