Is it possible to sync wem schedule adherence via byoc edge without hitting api limits?

is it possible to pull real-time schedule adherence data from wem through a byoc edge deployment? our team is trying to build a custom dashboard that shows live adherence metrics alongside queue stats, but hitting the standard wem api endpoints from our application server is causing rate limit issues during peak hours. we are deploying a byoc edge in us-east-1 to handle some of the load, but i’m unsure if the edge can proxy wem-specific api calls or if it’s strictly for routing and messaging.

we tried setting up a simple python script on the edge container to fetch /api/v2/wfm/scheduling/schedules, but the edge seems to strip out the necessary wfm scope tokens. are there any documented workarounds or specific manifest configurations needed to allow wem api passthrough? or is the recommended approach to cache the data locally on the edge and sync periodically? any insights would be appreciated. we are currently on the latest stable edge version 11.5.2.

Make sure you check the BYOC documentation first. The edge is for media routing, not WFM API proxying. Use webhooks or scheduled batch exports instead to avoid rate limits.

As far as I remember, the BYOC edge does not handle WFM API traffic. It strictly manages media streams, so proxying adherence data through it will not work. The suggestion above is accurate regarding the architecture.

Focus on scheduled batch exports for large datasets. For near real-time needs, implement webhooks to push updates directly. This approach respects API rate limits better than polling, which is crucial when managing high concurrency.