mergespecs direct Act-On to handle specifics when using the Update or Merge a list endpoint. When you append or update an existing list, mergespecs is required.

Include options below as a text body for the mergespecs parameter.

Options

Name	Required/Optional	Data Type	Description
mergeMode	Required	String	One of the following modes to use in implementing merge: APPEND; simple append APPEND_NO_DUPLICATES; append while skipping duplicates UPSERT; update existing and insert new records UPDATE_ONLY; update existing records. REPLACE: replace the entire contents of the list with the uploaded records. Any records in the list that are not in the uploaded records are deleted.
dstListId	Required	String	Id of the list being updated
columnMap	Required	Array List	columnMap is not currently supported and this functionality will be added in a planned v2 revision of this endpoint. columnMap must currently be specified as "columnMap": [] and your source and destination lists must have a 1:1 column index.
createSegment	Optional	String	If set to 1, creates a segment from records merged into the destination list.
mergeKeyHeading	Optional	String	heading name in the source data used to merge data into the destination list. If this is not specified, it uses the identified EMAIL column. (default = EMAIL)

Example

--form 'mergespecs="[
    {
        \"dstListId\": \"l-0001\",
        \"mergeMode\": \"UPSERT\",
        \"columnMap\": [],
        \"createSegment\": \"1\",
				\"mergeKeyHeading\": \"EMAIL\"
    }
]"' \