Tenant Server V1

post_access_searchUser

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

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

**post_access_searchUserResponse** Parameters:
Name	Parameter	Data Type	Required	Description
list	form	List<employeeInfo>	No

**baseResponse** Parameters:
Name	Parameter	Data Type	Required	Description
result	form	int	No
message	form	string	No

**employeeInfo** Parameters:
Name	Parameter	Data Type	Required
idnumber	form	string	No
username	form	string	No
name	form	string	No
email	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_access_searchUser HTTP/1.1 
Host: sdk.lovettcommercial.com 
Content-Type: application/xml
Content-Length: length

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

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

<post_access_searchUserResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TenantSDK.post.admin.access">
  <message xmlns="http://schemas.datacontract.org/2004/07/TenantSDK.post">String</message>
  <result xmlns="http://schemas.datacontract.org/2004/07/TenantSDK.post">0</result>
  <list>
    <employeeInfo>
      <email>String</email>
      <idnumber>String</idnumber>
      <name>String</name>
      <username>String</username>
    </employeeInfo>
  </list>
</post_access_searchUserResponse>