Skip to main content
Webhooks let Gecko react to activity in your repositories, running a PR scan when a pull or merge request opens, and tracking pushes. Gecko generates the webhook URL and secret when you connect a provider; you add them in your provider’s settings.
This page covers inbound webhooks from your Git provider to Gecko. To have Gecko push scan and finding events to your systems, see Webhook events in the API reference.

Endpoints, events, and verification

The GitHub App’s webhook is managed by Gecko, so there is nothing to configure on GitHub. For GitLab, use the exact URL and secret shown in Gecko when you connect; secrets are generated per team.

GitHub

The Gecko GitHub App ships with its webhook, so installing the App is the whole setup. GitHub signs each delivery with an HMAC-SHA256 signature in the X-Hub-Signature-256 header, and Gecko rejects any delivery whose signature doesn’t verify. Each delivery is processed once, keyed by its X-GitHub-Delivery ID, so GitHub’s retries don’t trigger duplicate scans.

GitLab

GitLab sends your secret token verbatim in the X-Gitlab-Token header. Gecko compares it against the per-team secret generated at connection time.
Enable Vulnerability events in GitLab if you want findings to flow into GitLab’s Security Dashboard via vulnerability export.

Network direction

Webhooks are outbound from your instance to Gecko at app.gecko.security. This is the opposite direction from cloning and API calls. Your network must be able to reach app.gecko.security on HTTPS, but webhooks don’t require you to allowlist Gecko’s IP addresses; those are for the outbound paths.

Troubleshooting

The secret doesn’t match. Re-copy the secret from Gecko into the provider’s secret field.
Confirm the right events are enabled (pull/merge request and push) and that the webhook delivery log in your provider shows 2xx responses.