Quick question about configuring SIP trunk registration details across multiple Genesys Cloud organizations using the Platform API within a Premium AppFoundry integration. We are attempting to automate the setup process for new tenants, but the PUT /api/v2/telephony/sip/lines endpoint consistently returns a 403 Forbidden error. The OAuth token is generated with the telephony:sip:write scope and validated against the target organization’s tenant ID.
The integration handles multi-org provisioning, so context switching is managed correctly. The payload structure matches the schema documentation, yet the API rejects the request immediately. No additional error details are provided in the response body, making troubleshooting difficult.
Here is the payload being sent:
{
"name": "External Trunk",
"sipAddress": "sip.provider.com",
"sipPort": 5060,
"protocol": "TCP",
"transport": "TLS",
"mediaEncryption": "SRTP"
}
Is there a specific permission requirement beyond the standard scope for modifying SIP configurations via API in a multi-tenant AppFoundry context? Any insights into hidden validation rules would be appreciated.