The bulk export job for screen recordings terminates with HTTP 422 Unprocessable Entity. The error response indicates a validation failure on the recording_type field, specifically stating that SCREEN is not a valid value for the requested data action scope.
We are processing a legal discovery request requiring chain of custody metadata for digital channel interactions. The API call targets /v2/recordings/exports with the standard payload structure used for voice recordings, but adapted for screen capture assets stored in our S3 bucket.
The configuration used in the Data Action is as follows:
export_config:
scope:
recording_type: SCREEN
date_range:
start: 2023-10-01T00:00:00Z
end: 2023-10-07T23:59:59Z
metadata:
include_chain_of_custody: true
include_legal_hold: true
destination:
type: s3
bucket: legal-archive-eu-west-1
Voice recording exports with identical IAM permissions and S3 policies succeed without issue. The recording_type enumeration in the documentation lists VOICE, CHAT, and SCREEN as valid types. However, the 422 error persists when SCREEN is specified. Is there a known limitation or separate endpoint required for screen recording bulk exports in the current API version? The audit trail shows the job fails immediately upon validation, before any S3 write operations occur.