| POST | /profile/purge/{SubscriptionId} |
|---|
import Foundation
import ServiceStack
public class ProfilePurgePost : Codable
{
public var profilePurgeContainer:ProfilePurgeContainer?
public var subscriptionId:String?
required public init(){}
}
public class ProfilePurgeContainer : Codable
{
public var transactionDate:Date?
public var retiredProfileId:String?
public var sourceId:ProfileMergePurgeSource?
public var importSource:String?
public var importSourceId:String?
public var cendynPropertyID:String?
required public init(){}
}
public enum ProfileMergePurgeSource : String, Codable
{
case Other
case Messaging
case DirectDBExtract
case ReportImport
}
public class Response : Codable
{
public var statusCode:String?
public var recordCount:Int?
public var errorCount:Int?
required public init(){}
}
To override the Content-type in your clients, use the HTTP Accept Header, append the .xml suffix or ?format=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>