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 .json suffix or ?format=json

To embed the response in a jsonp callback, append ?callback=myCallback

HTTP + JSON

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/json
Content-Type: application/json
Content-Length: length

{"profilePurgeContainer":{"transactionDate":"0001-01-01T00:00:00.0000000","retiredProfileId":"String","sourceId":"Other","importSource":"String","importSourceId":"String","cendynPropertyID":"String"},"subscriptionId":"String"}

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

{"statusCode":"String","recordCount":0,"errorCount":0}