Genesys Cloud - Main

Hi Team,

Our client has a requirement to  upload contact lists from an external system and maintains a mapping between their internally generated Lead ID and the Genesys Contact ID. (Lead ID will be a column in the contact list)

They plan to upload approximately 1.5 million contacts at the beginning of each month and can also upload them in batches.

One option is to use the following API:

POST /api/v2/outbound/contactlists/{contactListId}/contacts

Based on community discussions, I understand that a maximum of 1,000 contacts can be added in a single API request. The advantage of this approach is that the API response returns the Genesys Contact ID, which the client can use as a unique reference and map back to their Lead ID.

However, uploading 1.5 million contacts would require approximately 1,500 API requests. The client would like to understand the expected processing time per request and the overall time required to upload all contacts.

Option 2 

Another option is to use a CSV import for bulk uploads. We could include the client's Lead ID as a custom column in the CSV file so that it is stored in the contact list.

However, in this approach, how can the client obtain the Genesys Contact ID that is generated for each imported contact? Is there a supported way to retrieve the mapping between the imported Lead ID and the corresponding Genesys Contact ID after the CSV import is completed?

Has anyone implemented a similar solution or found a recommended approach for this use case?

#Outbound

------------------------------
Nivedraj P
x
------------------------------

If I am understanding ask correctly I did something like this a couple years ago.

My notes indicate the ID in the POST request in Option 1 can be YOUR unique Lead Id, emphasis on it being Unique. That will become the contact Id and can be referenced as such without a need to link to a Genesys generated GUID (which it does when using UI to create).

The other side of that which was useful is you can also have these Lead Ids in a DNC list if you need to prevent any being called.

The below payload is from my old notes so may be out of date now, but shows the idea. Where UniqueId would be your lead Id

		[
		  {
		    "id": "UniqueId1",
		    "contactListId": "13a8e583-4bb8-4def-bfdf-62b64085a3b8",
		    "data": {
		      "Lead Ref": "102000",
		      "First Name": "FirstName 1",
		      "Last Name": "LastName 1",
		      "CreatedOn": "2023-11-06T12:30:00.000",
		      "Tel1": "0781500000"
		    },
		    "callable": true,
		    "phoneNumberStatus": {
		      "Tel1": {
		        "callable": true
		      }
		    },
		    "contactableStatus": {
		      "Voice": {
		        "contactable": true
		      }
		    }
		  }
		]

------------------------------
Simon Brown
Maintel Europe Limited
Senior Applications Consultant
------------------------------