Quick question about the audit trail for our weekly schedule exports. We are strictly adhering to compliance requirements that mandate full visibility into who accessed agent PII during the publishing phase. Every Friday at 10:00 AM CST, our automated script triggers the /api/v2/wfm/schedules/exports endpoint to generate the CSV for payroll integration.
The issue is that the standard Admin audit logs show the API user action but do not capture the specific schedule version ID or the agent count included in that payload. For our auditors, this lack of granularity is a major red flag. We need to prove exactly which data set was extracted and when.
Is there a way to enrich these logs via the API response headers, or should we be implementing a custom webhook to capture the export metadata before the file is generated? We tried parsing the response body but it seems the detailed metadata is stripped after the initial job creation. Any workarounds for tracking this without building a whole new logging infrastructure?