RHP_API

DateFinderGetMyDate

The following routes are available for this service:
GET	/User/DateFinder

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.

GET /User/DateFinder HTTP/1.1 
Host: tstsrvs.redhotpie.com.au 
Accept: application/xml

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

<ArrayOfDateFinderMyDateItem xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/RHP_API.ServiceModel">
  <DateFinderMyDateItem>
    <AgeMax>0</AgeMax>
    <AgeMin>0</AgeMin>
    <CanHost>false</CanHost>
    <City>String</City>
    <Comment>String</Comment>
    <CountryName>String</CountryName>
    <DateHeld>0001-01-01T00:00:00</DateHeld>
    <DateHeldUtcIso>String</DateHeldUtcIso>
    <DisplayDate>String</DisplayDate>
    <ID>0</ID>
    <Location>String</Location>
    <OpenForList xmlns:d3p1="http://schemas.microsoft.com/2003/10/Serialization/Arrays">
      <d3p1:string>String</d3p1:string>
    </OpenForList>
    <OpenForTypes>0</OpenForTypes>
    <SeekingTypeList xmlns:d3p1="http://schemas.datacontract.org/2004/07/RHP.ServiceHelper.Model">
      <d3p1:LookupValue>
        <d3p1:ListID>0</d3p1:ListID>
        <d3p1:Text>String</d3p1:Text>
        <d3p1:TextAbbr>String</d3p1:TextAbbr>
        <d3p1:Value>0</d3p1:Value>
        <d3p1:IsMatch>false</d3p1:IsMatch>
      </d3p1:LookupValue>
    </SeekingTypeList>
    <SeekingTypes>0</SeekingTypes>
    <ShortComment>String</ShortComment>
    <StateName>String</StateName>
    <StateNameAbbr>String</StateNameAbbr>
    <InterestCount>0</InterestCount>
    <IsCommentRejected>false</IsCommentRejected>
    <IsCommentVisible>false</IsCommentVisible>
  </DateFinderMyDateItem>
</ArrayOfDateFinderMyDateItem>