Tenant Server V1

post_venuelist

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

**post_venuelist** Parameters:
Name	Parameter	Data Type	Required
token	query	string	Yes
tokensecret	query	string	Yes
email	query	string	Yes

**post_venuelistResponse** Parameters:
Name	Parameter	Data Type	Required	Description
list	form	List<post_venueInfo>	No

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

**post_venueInfo** Parameters:
Name	Parameter	Data Type	Required
idnumber	form	int	No
idcia	form	int	No
idproject	form	string	No
venuename	form	string	No
ledger	form	string	No
eventyn	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_venuelist HTTP/1.1 
Host: sdk.lovettcommercial.com 
Content-Type: application/xml
Content-Length: length

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

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

<post_venuelistResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TenantSDK.post.postevent">
  <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>
    <post_venueInfo>
      <eventyn>false</eventyn>
      <idcia>0</idcia>
      <idnumber>0</idnumber>
      <idproject>String</idproject>
      <ledger>String</ledger>
      <venuename>String</venuename>
    </post_venueInfo>
  </list>
</post_venuelistResponse>