Why is this setting causing a 403 Forbidden error when attempting to export chat transcripts with legal hold metadata?
We are processing a discovery request for digital channel interactions, specifically chat and SMS, in the eu-west-1 region. The bulk export job is initiated via the POST /api/v2/recordings/exports endpoint using the Python SDK version 1.5.2. The request payload includes includeLegalHoldMetadata: true and filters for interactions within a specific date range. The service account used has security:pii:manage and recording:export:admin scopes, which worked for voice recordings last week. However, for digital channels, the job fails immediately with a 403 status code and the message “Access denied to legal hold metadata for digital channel interactions”. The chain of custody requirements for this case mandate that we preserve the exact metadata from the source, so we cannot simply export the transcript text without the hold indicators. We have verified that the legal hold flags are correctly applied to the interactions in the UI. The error persists even when using a different service account with broader permissions. Is there a specific scope or configuration required for exporting legal hold metadata from digital channels that differs from voice recordings? We need to maintain audit trail integrity for the export job.