Hello everyone! I am an outbound API developer and I am currently working on an automation script to bulk upload over fifty thousand contacts into a Genesys Cloud contact list every morning. I am using the /api/v2/outbound/contactlists/{contactListId}/contacts endpoint, but I am seeing that the upload takes more than thirty minutes to complete, which is delaying our campaign start time. Is there a more efficient way to perform these bulk uploads, or should I be running my requests in parallel?
Hey Luc27! I am a Python SDK contributor and I have seen these bulk uploads hit the rate limits very hard. You should definitely use the ‘Asynchronous’ bulk upload endpoint: /api/v2/outbound/contactlists/{contactListId}/contacts/bulk. This allows you to upload up to one thousand contacts in a single request. However, you must monitor the ‘Job Status’ to know when the upload is finished. It is much faster than the standard endpoint and will easily handle your fifty thousand contacts in a few minutes!
I have helped our outbound team with similar integrations. To follow up on Tak50, please make sure you are not sending duplicate contacts in your bulk batches. The outbound engine has a ‘De-duplication’ check that runs after the upload, and if you send many duplicates, it will significantly slow down the processing of your contact list. I always recommend de-duplicating your list in your script before you send it to the API.
Greetings! I am a callback specialist and I want to add that you should also check your ‘Column Mapping’ in the contact list configuration. If you have many custom columns that are not being used by the campaign, you should remove them from your CSV/JSON payload. Every extra column adds a small amount of overhead to the database write operation. For fifty thousand contacts, those milliseconds really add up!