Hi all,
We are facing a critical gap in our chain of custody documentation when exporting call recordings for legal discovery requests. Our environment is Genesys Cloud (London region, standard cloud). We rely on the bulk recording export API to pull audio files along with their metadata to an S3 bucket for long-term retention.
The issue is that while the call_recording object in the export includes startTime, endTime, and participants, it does not include the specific scriptId or scriptVersion that the agent was using during the interaction. For legal compliance, we must prove exactly what version of the script the agent followed, as these scripts change frequently.
We have verified that the conversation:fetch API returns the scriptId in the wrapup code or via the script object if it was active. However, when we trigger a bulk export job using the POST /api/v2/recordings/search endpoint with a date range filter, the resulting JSON metadata lacks this field entirely.
We tried including scriptId in the fields parameter of the request, but the API returns a 400 Bad Request stating that scriptId is not a valid field for the recording search entity.
Is there a known workaround to enrich the bulk export metadata with script version details? Or is there a separate endpoint we should be querying to map conversationId to scriptVersion at scale? We cannot manually fetch each conversation via API due to the volume of recordings (approx. 50k per month).
Any guidance on how to maintain this data integrity for legal holds would be appreciated.