How should I properly to structure the payload for the POST /api/v2/analytics/screen-recordings/exports endpoint when filtering for specific recording types within our AppFoundry integration?
We are currently developing a custom dashboard that aggregates screen recording metadata for compliance review. The integration uses a service account with the screen-recordings:read and analytics:export permissions. When we attempt to initiate an export job, we are receiving a 400 Bad Request error. The response body indicates that the recordingType filter value is invalid, despite using the exact string values documented in the Genesys Cloud API reference.
The request payload is structured as follows:
{
"query": {
"recordingType": "screen",
"dateRange": {
"from": "2023-10-01T00:00:00.000Z",
"to": "2023-10-31T23:59:59.999Z"
}
},
"exportType": "csv"
}
The error response is:
{
"code": "badRequest",
"message": "Invalid recording type specified. Valid values are: all, audio, video."
}
This is confusing because the screen recording type is clearly visible in the UI and when fetching individual recordings via GET /api/v2/screen-recordings/{screenRecordingId}. We have verified that the OAuth token is valid and has not expired. We are also checking the rate limits, but this is a single request, so throttling should not be an issue.
We have tried using video as the recording type, but that returns empty results, even though we know screen recordings were created during the specified date range. It seems like the export API might be treating screen recordings differently than standard audio/video recordings.
Is there a specific filter value or additional parameter required to export screen recordings via the Analytics API, or is this a known limitation where screen recordings must be fetched individually?