CenResService

ProfilePurgePost

The following routes are available for this service:
POST	/profile/purge/{SubscriptionId}

**ProfilePurgePost** Parameters:
Name	Parameter	Data Type	Required	Description
ProfilePurgeContainer	body	ProfilePurgeContainer	No
SubscriptionId	path	string	No

**ProfilePurgeContainer** Parameters:
Name	Parameter	Data Type	Required
TransactionDate	form	DateTime	No
RetiredProfileId	form	string	No
SourceId	form	ProfileMergePurgeSource	No
ImportSource	form	string	No
ImportSourceId	form	string	No
CendynPropertyID	form	string	No

**ProfileMergePurgeSource** Enum:
Other
Messaging
DirectDBExtract
ReportImport

**Response** Parameters:
Name	Parameter	Data Type	Required
StatusCode	form	string	No
RecordCount	form	int	No
ErrorCount	form	int	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 /profile/purge/{SubscriptionId} HTTP/1.1 
Host: cert.cendyn.com 
Accept: application/xml
Content-Type: application/xml
Content-Length: length

<ProfilePurgePost xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/CenResSS.ServiceModel">
  <ProfilePurgeContainer>
    <CendynPropertyID>String</CendynPropertyID>
    <ImportSource>String</ImportSource>
    <ImportSourceId>String</ImportSourceId>
    <RetiredProfileId>String</RetiredProfileId>
    <SourceId>Other</SourceId>
    <TransactionDate>0001-01-01T00:00:00</TransactionDate>
  </ProfilePurgeContainer>
  <SubscriptionId>String</SubscriptionId>
</ProfilePurgePost>

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

<Response xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/CenResSS.ServiceModel">
  <ErrorCount>0</ErrorCount>
  <RecordCount>0</RecordCount>
  <StatusCode>String</StatusCode>
</Response>