Summary
Genesys Cloud is updating the Recording Batch Download API to enforce the permissions already documented for creating a batch download job.
Currently, when a request is submitted to:
POST /api/v2/recording/batchrequests
the batch download job is accepted and processed asynchronously. During processing, authorization is evaluated for each requested recording.
Depending on the recording type, access requires at least one of the following permissions:
- recording:recording
- recording:recordingSegment
- recording:screenRecording
- recording:snippetRecording
For recordings the user is authorized to access, the job prepares the recording for download and includes a successful result in the job output. For recordings the user is not authorized to access, an error is included in the job output.
With this change, permission validation will also occur when the batch download job is created. If the user has none of the documented recording permissions, the POST request will be rejected immediately with an HTTP 403 Forbidden response instead of creating a job that cannot return any successful recording results.
The API documentation already identifies these permissions as required for this endpoint.
Effective Date
Monday, November 9, 2026
Details
The Recording Batch Download API currently documents that one of the supported recording permissions is required. However, the POST endpoint does not currently enforce this requirement when the batch job is created.
As a result, a user without any of the required permissions can create a batch download job, even though authorization checks performed during asynchronous processing will prevent access to every requested recording.
This change aligns runtime behavior with the documented API permission requirements and prevents creation of batch download jobs that cannot return any successful recording results.
Customer Impact
Customers submitting a batch download job without any of the following permissions will receive an HTTP 403 Forbidden response when attempting to create the job:
- recording:recording
- recording:recordingSegment
- recording:screenRecording
- recording:snippetRecording
Previously, the job creation request was accepted and the authorization failures were returned later as part of the asynchronous job results.
Customers with at least one of the documented permissions will experience no change in behavior. Authorization checks for individual recordings will continue to occur during job processing.
Customer Action Required
Customers using the Recording Batch Download API should ensure that users or OAuth clients creating batch download jobs have at least one of the documented recording permissions.
Integrations should also be prepared to handle an HTTP 403 Forbidden response when the caller does not have any of the required permissions.
Impacted Resources
POST /api/v2/recording/batchrequests
Issue References
REC-13032
Contacts
@Chad Fraser Please reply to this announcement with any questions. This helps the wider developer community benefit from the discussion. We encourage you to use this thread before contacting the designated person directly. Thank you for your understanding.