What is the reason the POST /api/v2/recordings/bulkexport endpoint is returning a 400 Bad Request when I include specific legal hold metadata tags? We are processing a large volume of digital channel recordings for a legal discovery request in the London timezone. The environment is Genesys Cloud EU-West-1. I have verified that the S3 bucket permissions are correct and the integration is active. The issue appears only when I attempt to filter by a custom attribute that was added to the recording metadata via the API during the call session.
The error response indicates a validation failure on the filter object. Specifically, the system claims the attribute name is invalid, even though it exists in the recording metadata. Here is the error payload we are seeing:
{
"errors": [
{
"code": "BadRequest",
"message": "Filter attribute 'legal_hold_tag' is not a valid recording metadata field for bulk export."
}
]
}
We have tried using the exact attribute key from the GET /api/v2/recordings/{recordingId} response. The attribute is clearly present in the individual recording details. However, the bulk export API seems to ignore custom metadata fields unless they are part of the standard set. Is there a way to register custom metadata fields for use in bulk export filters? Or is this a limitation of the current API version? We need to ensure chain of custody compliance by exporting only recordings with specific legal hold tags. Any guidance on how to resolve this validation error would be appreciated. We are using the latest SDK version for Python.