Just noticed that our AppFoundry integration is failing to synchronize tenant configurations across multiple Genesys Cloud organizations when using the Bring Your Own Cloud (BYOC) Edge API. The POST /api/v2/byp/edges/tenants call returns a 403 Forbidden error with the message “Insufficient permissions to access resource” despite the OAuth token having the byp:edges:write scope.
Context:
Our partner application manages edge configurations for enterprise clients across multiple Genesys Cloud organizations. We use multi-org OAuth tokens to provision and update BYOC edge settings programmatically. The integration has been stable for the past six months, but we started encountering these 403 errors after the recent platform update on March 15th. The error occurs consistently when attempting to update tenant-specific edge configurations via the Platform API.
The request payload validates against the API schema, and the OAuth token has the required scopes (byp:edges:read, byp:edges:write). We’ve verified that the token is valid and has not expired. The issue persists across multiple organizations and edge configurations, suggesting a systemic problem rather than an isolated configuration error.
We’ve also checked the API rate limits and confirmed that we’re not being throttled. The 403 error is returned immediately, indicating a permissions issue rather than a rate-limiting problem.
Question:
Has the BYOC Edge API permissions model changed in the recent platform update? If so, what are the new requirements for managing multi-org tenant configurations via the Platform API? We need to update our integration to comply with any new permission requirements or API changes.