Skip to main content
POST
Merge contact lists
Merges contacts from one or more source lists into a target list. Optionally deletes the source lists after merging. This is useful when payload limits require creating multiple sub-lists that should logically be one list. Instead of leaving SDRs with fragmented lists in the dialer, merge them server-side into a single clean list.

Path Parameters

  • id (required, string): Target contact list ID to merge into.

Request Body

FieldTypeRequiredDescription
source_list_idsstring[]YesIDs of the source lists to merge into the target (1–20 lists)
delete_sourcesbooleanNoWhether to delete the source lists after merging. Default: false

Limits

  • Max 20 source lists per merge request
  • The target list cannot appear in source_list_ids (it will be ignored)

Example Request

Response (201)

Returns the updated target contact list.

Errors

StatusDescription
404Target contact list not found

Authorizations

x-api-key
string
header
required

Path Parameters

id
string
required

Target contact list ID to merge into

Example:

"507f1f77bcf86cd799439011"

Body

application/json
source_list_ids
string[]
required

IDs of the source lists to merge into the target list

Required array length: 1 - 20 elements
Example:
delete_sources
boolean
default:false

Whether to delete the source lists after merging

Response

Lists merged successfully

_id
string
required

Unique identifier

name
string
required

Contact list name

source
enum<string>
required

List source

Available options:
csv,
hubspot,
salesforce,
manual
user
object
total_contacts
integer

Number of contacts