I am currently helping our compliance team with a massive recording export project. We need to move over one million historical recordings from Genesys Cloud to our corporate archive. I am using the Recording API to trigger the exports, but I am finding that the process is extremely slow and I am hitting my daily export quota before I even finish one month of data. Is there a way to request a quota increase or a more efficient method for bulk exporting millions of recordings?
Hey Ren43! I am a voice biometrics enthusiast and I have spent a lot of time with the Recording API. One million recordings is a lot! You should not use the single-conversation export endpoint. You should use the ‘Recording Jobs’ API. This allows you to submit a bulk request that the platform processes in the background. You can export up to one hundred thousand recordings per job. It is much more efficient and it has its own separate quota from the standard API requests.
I want to add that when you use the Recording Jobs API, you should specify an S3 bucket as the destination. This allows Genesys Cloud to push the files directly to your storage without you having to download them one by one. Also, make sure your S3 bucket has the correct bucket policy to allow the Genesys Cloud AWS account to write the files. I have seen many jobs fail because of a ‘Permission Denied’ error on the AWS side.
I have automated these recording exports using Workato. To follow up on Chi63, please be aware that the Recording Jobs API also has a concurrency limit. You can only have five active jobs at any given time. If you try to submit more, you will get a 429 error. You should write a script that monitors the status of your jobs and only submits a new one when an existing one is complete. This will help you stay within the limits and finish your million-recording export as fast as possible.