CenResService

ProfileMergePost

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

import Foundation
import ServiceStack

public class ProfileMergePost : Codable
{
    public var profileMergeContainer:ProfileMergeContainer?
    public var subscriptionId:String?

    required public init(){}
}

public class ProfileMergeContainer : ProfilePurgeContainer
{
    public var winningProfileId:String?
    public var transferredCendynID:String?

    required public init(){ super.init() }

    private enum CodingKeys : String, CodingKey {
        case winningProfileId
        case transferredCendynID
    }

    required public init(from decoder: Decoder) throws {
        try super.init(from: decoder)
        let container = try decoder.container(keyedBy: CodingKeys.self)
        winningProfileId = try container.decodeIfPresent(String.self, forKey: .winningProfileId)
        transferredCendynID = try container.decodeIfPresent(String.self, forKey: .transferredCendynID)
    }

    public override func encode(to encoder: Encoder) throws {
        try super.encode(to: encoder)
        var container = encoder.container(keyedBy: CodingKeys.self)
        if winningProfileId != nil { try container.encode(winningProfileId, forKey: .winningProfileId) }
        if transferredCendynID != nil { try container.encode(transferredCendynID, forKey: .transferredCendynID) }
    }
}

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(){}
}

Swift ProfileMergePost DTOs

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/merge/{SubscriptionId} HTTP/1.1 
Host: cert.cendyn.com 
Accept: application/xml
Content-Type: application/xml
Content-Length: length

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

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>