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 theX-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 theX-Gitlab-Token header.
Gecko compares it against the per-team secret generated at connection time.
Network direction
Webhooks are outbound from your instance to Gecko atapp.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
Deliveries fail with 401 or 403
Deliveries fail with 401 or 403
The secret doesn’t match. Re-copy the secret from Gecko into the provider’s
secret field.
No PR scans are triggering
No PR scans are triggering
Confirm the right events are enabled (pull/merge request and push) and that
the webhook delivery log in your provider shows
2xx responses.