My configuration keeps failing…
- Provider: gc-provider v2.0.8
- Platform: Genesys Cloud (AU region)
- Tool: Terraform 1.6.4
- Endpoint: /api/v2/messaging/channels
- Error: 400 Bad Request
Deploying a new messaging channel via HCL fails consistently during the terraform apply phase. The pipeline uses GitHub Actions for promotion from Dev to Prod. The configuration defines a standard messaging channel with an associated webhook for inbound message handling.
hcl
resource "genesyscloud_messaging_channel" "support_chat" {
name = "Support Chat Channel"
channel_id = "support-chat-id"
enabled = true
webhook {
url = "https://our-internal-service.com/gc/webhook"
secret = "abc123secret"
}
}
The API returns a 400 Bad Request with the following payload:
{
"code": "bad.request",
"message": "Invalid webhook configuration",
"details": [
{
"code": "invalid.url",
"message": "Webhook URL must be publicly accessible and support HTTPS"
}
]
}
The URL is publicly accessible and supports HTTPS. Verified via curl and browser access. The internal service logs show no incoming requests from Genesys Cloud during the apply phase.
Checked the GC CLI documentation for messaging channels. The schema seems correct. The webhook secret is base64 encoded as required. No typos in the URL.
Is there a specific requirement for the webhook endpoint during channel creation? Does Genysus Cloud perform a synchronous validation call that might be blocked by our firewall rules? The error message is generic. No further details in the audit logs.
Looking for insights on how to debug this 400 error. The same configuration works in the sandbox environment. Production environment has stricter network policies.
Any help appreciated. Stuck on this for two days. Blocking the release.