Genesys Cloud - Main

Yes, those give you a start, but better to reference these articles:
Bulk delete\export of recordings (genesys.cloud)

Download Recordings (genesys.cloud)

They step you through the process individually or in bulk.

Now, if you want a really easy way - just copy recordings to your own S3 bucket through a policy and then store those someplace safe.
Add the AWS S3 recording bulk actions integration - Genesys Cloud Resource Center (mypurecloud.com)

@Robert Wakefield-Carl 

Thank you for the information. We will check the links and the S3 bucket option. 

Yes, those give you a start, but better to reference these articles:
Bulk delete\export of recordings (genesys.cloud)

Download Recordings (genesys.cloud)

They step you through the process individually or in bulk.

Now, if you want a really easy way - just copy recordings to your own S3 bucket through a policy and then store those someplace safe.
Add the AWS S3 recording bulk actions integration - Genesys Cloud Resource Center (mypurecloud.com)

If you don't want to download the entire Conversation JSON, you can do a query that will return a limited set of columns for many Conversations at once. We did this because we don't have use to store every minor detail of the Conversation, just the major parts. 

Also, the Conversation JSON references other objects in Genesys by a GUID sometimes, so you should probably download the configuration data occasionally so that you can reconcile some things. 

And lastly, if you actually intend do analytics on this data, then I recommend using the media-specific Conversation Detail API because it gives a more human-readable view of the Conversation. For example:

/api/v2/conversations/emails/{conversationId}
/api/v2/conversations/calls/{conversationId}

@Robert Wakefield-Carl 

Thank you for the information. We will check the links and the S3 bucket option. 

Yes, those give you a start, but better to reference these articles:
Bulk delete\export of recordings (genesys.cloud)

Download Recordings (genesys.cloud)

They step you through the process individually or in bulk.

Now, if you want a really easy way - just copy recordings to your own S3 bucket through a policy and then store those someplace safe.
Add the AWS S3 recording bulk actions integration - Genesys Cloud Resource Center (mypurecloud.com)

Hi

Others made some suggestions already.

Another approach is to use the Genesys GC.exe tool, that paired with other tools (Powershell) in my example, allows you to extract only details you need from the json responses.
Also do not need to "code" something for this approach other than some scripting skills, for example below to get just the ID and Name from a user api call

So I used gc.exe to extract agents json to a file (can be piped directly in powershell if required).

gc users list --autopaginate -p SG > C:\temp\SGAgents.json

Snippet in powershell script grabs just the Id and Name for use later. 

#User Ids and Name
$AgentjsonFilePath = "C:\temp\SGagents.json"
[PSObject] $agentsNames = Get-Content $AgentjsonFilePath | ConvertFrom-Json | Select-Object @{N="id";E={$_.entities.id}}, @{N="name";E={$_.entities.name}}

We also have a project in AWS to extract recordings to a bucket, with some of the basic metadata from conversation, to a customer AWS to get around the time period limitation in Genesys. AWS based web access to search and work on recordings.

Regards
Simon

I'm assuming they want a more automated approach to storing data. Have you checked out any of the AppFoundry blueprints on this, like:
https://appfoundry.genesys.com/filter/genesyscloud/listing/a9b23441-9334-45dd-b2a2-14e473fdba2c

There may also be AppFoundry Premium Apps that do what you want already. May be worth the extra cost instead of building/maintaining this all yourself:
Slidy Cloud Data Mart
A3S Automated Data Ingestion

Hi

Others made some suggestions already.

Another approach is to use the Genesys GC.exe tool, that paired with other tools (Powershell) in my example, allows you to extract only details you need from the json responses.
Also do not need to "code" something for this approach other than some scripting skills, for example below to get just the ID and Name from a user api call

So I used gc.exe to extract agents json to a file (can be piped directly in powershell if required).

gc users list --autopaginate -p SG > C:\temp\SGAgents.json

Snippet in powershell script grabs just the Id and Name for use later. 

#User Ids and Name
$AgentjsonFilePath = "C:\temp\SGagents.json"
[PSObject] $agentsNames = Get-Content $AgentjsonFilePath | ConvertFrom-Json | Select-Object @{N="id";E={$_.entities.id}}, @{N="name";E={$_.entities.name}}

We also have a project in AWS to extract recordings to a bucket, with some of the basic metadata from conversation, to a customer AWS to get around the time period limitation in Genesys. AWS based web access to search and work on recordings.

Regards
Simon

Hi

Others made some suggestions already.

Another approach is to use the Genesys GC.exe tool, that paired with other tools (Powershell) in my example, allows you to extract only details you need from the json responses.
Also do not need to "code" something for this approach other than some scripting skills, for example below to get just the ID and Name from a user api call

So I used gc.exe to extract agents json to a file (can be piped directly in powershell if required).

gc users list --autopaginate -p SG > C:\temp\SGAgents.json

Snippet in powershell script grabs just the Id and Name for use later. 

#User Ids and Name
$AgentjsonFilePath = "C:\temp\SGagents.json"
[PSObject] $agentsNames = Get-Content $AgentjsonFilePath | ConvertFrom-Json | Select-Object @{N="id";E={$_.entities.id}}, @{N="name";E={$_.entities.name}}

We also have a project in AWS to extract recordings to a bucket, with some of the basic metadata from conversation, to a customer AWS to get around the time period limitation in Genesys. AWS based web access to search and work on recordings.

Regards
Simon