SIP Trunk Registration 403 Forbidden on Multi-Org Premium App Provisioning

Is it possible to programmatically configure SIP trunk registration details across multiple Genesys Cloud organizations using the Platform API within a Premium AppFoundry integration? We are attempting to automate the deployment of telephony resources for new client tenants. The workflow involves creating the SIP trunk and immediately updating the registration settings. While the initial creation succeeds, the subsequent update request consistently returns a 403 Forbidden error, specifically citing insufficient permissions for the telephony:trunk:modify scope, despite the OAuth token possessing the required admin privileges. We have verified that the integration user holds the Site Administrator role in all target organizations. This behavior suggests a potential scoping issue or a delay in permission propagation during multi-org setup. Has anyone successfully implemented automated SIP trunk configuration in this context, or are there specific API sequence requirements we are missing?

2 Likes