Tenant Server V1

post_login

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

**post_login** Parameters:
Name	Parameter	Data Type	Required	Description
email	query	string	Yes
password	query	string	Yes

**post_loginResponse** Parameters:
Name	Parameter	Data Type	Required
result	form	int	No
message	form	string	No
idnumber	form	string	No
token	form	string	No
tokensecret	form	string	No
email	form	string	No
name	form	string	No
phone	form	string	No
homePhone	form	string	No
address	form	string	No
firstname	form	string	No
lastname	form	string	No
sms_activeyn	form	bool	No
sms_mobile	form	string	No
sms_verified	form	bool	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_login HTTP/1.1 
Host: sdk.lovettcommercial.com 
Content-Type: application/xml
Content-Length: length

<post_login xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TenantSDK.post.login">
  <email>String</email>
  <password>String</password>
</post_login>

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

<post_loginResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TenantSDK.post.login">
  <address>String</address>
  <email>String</email>
  <firstname>String</firstname>
  <homePhone>String</homePhone>
  <idnumber>String</idnumber>
  <lastname>String</lastname>
  <message>String</message>
  <name>String</name>
  <phone>String</phone>
  <result>0</result>
  <sms_activeyn>false</sms_activeyn>
  <sms_mobile>String</sms_mobile>
  <sms_verified>false</sms_verified>
  <token>String</token>
  <tokensecret>String</tokensecret>
</post_loginResponse>