Is it possible to automate the extraction of schedule adherence metrics using the Genesys Cloud provider for Terraform or the GC CLI tool? Current environment is AU-1 BYOC. Provider version genesyscloud v1.22.0. CLI version 1.0.105. The goal is to integrate WFM reporting into the CI/CD pipeline for automated compliance checks. Need to pull adherence data for a specific group over the last 7 days. Tried using the analytics API endpoint directly from a GitHub Actions runner with OAuth2 service account credentials. The endpoint https://api.au-gcp.genesiscloud.com/v2/analytics/reporting/query returns a 403 Forbidden error when attempting to access WFM-specific data types. The service account has “admin:reporting” and “admin:wfm” roles assigned. Verified permissions in the UI. The error response indicates insufficient privileges for the requested resource type. Code snippet from the action workflow shows the curl command used to query the API. The request body includes the correct date range and group ID. The issue seems to be related to the specific data type “schedule-adherence” requiring additional permissions or a different authentication method. No documentation found on how to grant API access to WFM analytics data for service accounts. Terraform does not have a resource for querying analytics data. Only configuration resources exist. Need a programmatic way to fetch this data for validation in the deployment pipeline. Is there a specific role or permission set required for API access to WFM reports? Or is this data only accessible via the web UI and scheduled email reports? Any workarounds using the GC CLI or custom scripts would be appreciated. The current manual process is too slow for our deployment cycles. Need to ensure that WFM configurations do not negatively impact adherence scores before promoting changes to production. The error log from the runner shows the full HTTP request and response headers. The token is valid and works for other API calls like user management and routing configuration. The issue is isolated to WFM analytics endpoints. Please advise on the correct approach to access this data programmatically. Thanks.