quick question about the analytics api v2 endpoint /api/v2/analytics/conversations/details/query. we are running a legal discovery request that requires full chain of custody metadata for webrtc digital channel sessions. specifically, we need the legal_hold_status and custody_chain_id fields populated in the response payload to satisfy compliance requirements for the current quarter.
the issue is that while the api returns basic conversation metrics and participant details correctly, the custom metadata fields required for our legal hold process are consistently null or missing entirely. we have verified that these fields are correctly populated in the raw recording metadata via the recording api v2, so the data exists in the system. however, when querying through analytics, the join seems to drop these specific attributes.
we are using the python sdk version 132.0.0 in our automation pipeline. the query payload includes the standard filters for conversation_type: webchat and channel: webrtc, along with the date range covering the last 30 days. the response status code is 200 ok, but the details array lacks the required compliance tags. we have also tried enabling the include_metadata: true flag in the request headers, but this does not appear to affect the output for digital channels in the same way it does for voice recordings.
is there a known limitation with the analytics api regarding webrtc metadata propagation? or is there a specific configuration in the architect flow or data model that needs to be adjusted to ensure these fields are indexed for analytics queries? we need to resolve this quickly as the discovery deadline is approaching, and manual extraction via s3 bucket polling is not scalable for the volume of sessions we are dealing with. any insights or workarounds would be appreciated.