api_auth

<back to all web services

SiteInvitationRequest

SiteInvitationRequest Parameters:
NameParameterData TypeRequiredDescription
SiteInvitationIDquerylongNo
SiteIDquerylongNo
GroupIDquerylong?No
PersonIDquerylong?No
FirstNamequerystringNo
LastNamequerystringNo
EmailquerystringNo
IsStrictEmailqueryboolNo
LanguageIDquerystringNo
Telephonequerylong?No
ExpirationTimequeryDateTime?No
RelationTypequerybyte?No
AcquaintancequerybyteNo
HaveMetInPersonqueryboolNo
RecognizeFacequeryboolNo
RecognizeVoicequeryboolNo
TrustLevelquerydecimalNo
IsPlusMemberqueryboolNo
PlusExpirationqueryDateTime?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/oneway/SiteInvitationRequest HTTP/1.1 
Host: 1.hyper.id 
Accept: application/xml
Content-Type: application/xml
Content-Length: length

<SiteInvitationRequest xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/Bitpub.Api.Auth.Common">
  <Acquaintance>0</Acquaintance>
  <Email>String</Email>
  <ExpirationTime>0001-01-01T00:00:00</ExpirationTime>
  <FirstName>String</FirstName>
  <GroupID>0</GroupID>
  <HaveMetInPerson>false</HaveMetInPerson>
  <IsPlusMember>false</IsPlusMember>
  <IsStrictEmail>false</IsStrictEmail>
  <LanguageID>String</LanguageID>
  <LastName>String</LastName>
  <PersonID>0</PersonID>
  <PlusExpiration>0001-01-01T00:00:00</PlusExpiration>
  <RecognizeFace>false</RecognizeFace>
  <RecognizeVoice>false</RecognizeVoice>
  <RelationType>0</RelationType>
  <SiteID>0</SiteID>
  <SiteInvitationID>0</SiteInvitationID>
  <Telephone>0</Telephone>
  <TrustLevel>0</TrustLevel>
</SiteInvitationRequest>