Skip to main content
Create, organize, and manage contact lists to segment your audience for targeted email campaigns.

Goal

By the end of this guide you will be able to create lists within a contact structure, list all existing lists, update list names, delete lists, duplicate a list, and merge multiple lists into one.

Prerequisites

  • An API key with contacts:write scope (for full list management) or contacts:read scope (for read-only access)
  • Your API base URL (found on the Settings > API Keys page)
  • A contact structure ID — lists belong to a contact structure. Retrieve yours with GET /api/contact-structure (see Manage Custom Fields)

Steps

1. Create a list

Create a new list within a contact structure. The only required field is name.
Response (201 Created):
Notes:
  • List type defaults to "static" (the only supported type currently)
  • List names can be up to 1,000 characters

2. List all lists (paginated)

Retrieve lists with pagination, sorting, and search support.
Response (200 OK):
Query parameters: To retrieve all lists without pagination (returns _id, name, and type only):

3. Get a single list

Response (200 OK):

4. Update a list

Rename a list by sending a PATCH request. You must include the current __v (version) value for optimistic concurrency control.
Response (200 OK):
Important: The __v field prevents conflicts when multiple clients update the same list. Always send the current __v value from your last GET response. If another update occurred in the meantime, you will receive a 400 error with a ConcurrencyError type.

5. Delete a list

Delete a single list by ID:
Response (204 No Content): Empty body. To delete multiple lists at once, send a DELETE to the lists collection endpoint:
Response (204 No Content): Empty body.

6. Duplicate a list

Create a copy of an existing list (contacts are copied to the new list).
Response (201 Created):

7. Merge lists

Combine two or more lists into a new list. Contacts from all source lists are added to the new list (duplicates are handled automatically).
Response (200 OK):
Notes:
  • The source lists are not deleted; they remain intact
  • The merged list is a new list containing all unique contacts from the source lists
  • At least one listId is required

Common Errors

Next Steps