Just noticed that the recent bulk export for SIP trunks via POST /api/v2/recordings/exports is stripping the legal_hold flag from the resulting JSON metadata. The Architect flow sets this correctly, and WhatsApp exports work fine. The S3 integration receives the file, but the chain of custody audit fails because the tag is absent in the manifest. Why is the SIP recording export ignoring the legal_hold attribute while digital channels respect it?
TL;DR: The export API likely requires explicit field selection.
Have you tried adding "fields": ["legal_hold"] to the POST body? The endpoint defaults to a slim schema unless you explicitly request custom metadata attributes in the query parameters.