Looking for advice on BYOC trunk registration failures. The initial trunk creation succeeds, but the subsequent registration step fails immediately with a 403 Forbidden error when attempting to transform the webhook payload for ServiceNow integration. The endpoint /api/v2/telephony/providers/edges returns valid metadata, yet the specific edge ID provided in the payload triggers an access denied response. Is there a specific scope requirement for the Data Action executing this transformation that is missing from the current OAuth token configuration?
You need to ensure the service account has telephony:edge:read scope, not just admin rights.
The Data Action runs in its own context. Missing scope causes the 403.
The main issue here is likely missing explicit scope in the service account credentials used by the Data Action. Ensure the account has telephony:edge:read access. Without this, the transformation fails with 403 even if admin rights exist elsewhere. Check these items:
- Service account scope configuration
- Edge ID validity in payload
- Webhook endpoint permissions