SIP Trunk Bulk Export 400 on Call Recording Metadata

  • Why does this setting… cause a failure when attempting to include recording_url in the filter for voice interactions?
  • Environment: Genesys Cloud BYOC EU-West-1
  • Endpoint: POST /api/v2/bulkexports/exportjobs
  • Error Response: 400 Bad Request
  • Error Message: Invalid filter: recording_url is not a valid property for telephony recordings.
  • Context: We are processing a legal discovery request requiring all SIP trunk recordings from the last quarter. The documentation suggests recording_url should be available for filtering voice data.
  • Observation: This endpoint works correctly for digital channels like SMS and WhatsApp where media attachments are explicit. However, for telephony, the API rejects the filter entirely.
  • Question: Is there a specific limitation for voice recording metadata in bulk exports? Or is there an alternative property we should use to isolate recordings with valid URLs? We need to ensure the chain of custody remains intact during the export to S3.