Tenant Server V1

<back to all web services

post_postvenueattentionlist

The following routes are available for this service:
All Verbs/post_postvenueattentionlist
post_postvenueattentionlist Parameters:
NameParameterData TypeRequiredDescription
tokenquerystringYes
tokensecretquerystringYes
emailquerystringYes
idpostvenuequerystringNo
post_postvenueattentionlistResponse Parameters:
NameParameterData TypeRequiredDescription
listformList<postvenueattention>No
baseResponse Parameters:
NameParameterData TypeRequiredDescription
resultformintNo
messageformstringNo
postvenueattention Parameters:
NameParameterData TypeRequiredDescription
idnumberformintNo
nameformstringNo
emailformstringNo

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

<post_postvenueattentionlist xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TenantSDK.post.postevent">
  <email>String</email>
  <idpostvenue>String</idpostvenue>
  <token>String</token>
  <tokensecret>String</tokensecret>
</post_postvenueattentionlist>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length

<post_postvenueattentionlistResponse 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>
    <postvenueattention>
      <email>String</email>
      <idnumber>0</idnumber>
      <name>String</name>
    </postvenueattention>
  </list>
</post_postvenueattentionlistResponse>