Calling GET /api/v2/conversations/{conversationId}/recordingmetadata/{recordingId} returns 404 Not Found when targeting recordings initiated on a customer’s BYOC edge. The same endpoint works flawlessly on public cloud instances using the same OAuth token. Has anyone encountered scope limitations for screen recording metadata on BYOC deployments?
1 Like