Support custom path prefixes for Checkmarx One self-hosted integration webhooks
A
AnilKumarReddy Gajulapalli
We’d like Checkmarx One self-hosted integration to support webhook endpoints with flexible path prefixes, instead of requiring all webhooks to be sent only to a fixed /integration/webhook path.
Current Limitation
At the moment, webhook requests are only accepted when they are sent to the exact /integration/webhook endpoint. If a webhook is sent to a prefixed path such as /checkmarx-one/integration/webhook, the request fails, even when traffic is correctly routed to the integration.
Requested Behavior
- Allow webhook endpoints to be exposed behind a single shared domain, for example: https://example.com/<integration>/integration/webhook
- Support path-based routing so different integrations can be reached via unique URL prefixes.
- Once a request reaches the integration, it should be accepted as long as the path ends with /integration/webhook, regardless of any preceding path segments.
Why This Is Important
- Simplifies infrastructure by avoiding the need for a separate DNS name per integration
- Makes it easier to manage IP allowlists, firewall rules, and security policies at the domain level
- Enables smoother promotion of integrations from development to production environments
- Aligns with common enterprise patterns that rely on a single domain with path-based routing