How do I test GitLab webhooks without deploying anything?

Create a free endpoint on webhooks.cc — sign in with GitHub or Google, or use a guest endpoint without an account — then configure it as your webhook URL: Project → Settings → Webhooks. Every delivery shows up live in the dashboard with full headers, body, and query parameters. To hit a local server, run whk tunnel and the CLI forwards each webhook to localhost.

Can I send a sample GitLab webhook without a GitLab account?

Yes. webhooks.cc ships GitLab templates (push, merge_request) with realistic payloads and correctly computed signature headers. Send them from the dashboard, the SDK, or the MCP server to exercise your handler end-to-end.

How do I verify GitLab webhook signatures?

GitLab signs each delivery with the x-gitlab-token header using Shared token comparison. webhooks.cc verifies these signatures for you: add your secret token to the endpoint and every captured request is marked valid or invalid in the dashboard.

Is the GitLab webhook tester free?

Yes. A free account gets you persistent endpoints, 50 requests per day, 7-day retention, and full CLI, SDK, and MCP access — no credit card. You can also try a guest endpoint without an account: up to 25 requests for 12 hours.

Test GitLab webhooks

GitLab sends webhooks for pushes, merge requests, pipelines, issues, and tag events on projects and groups. Capture them on a free webhooks.cc endpoint to see exactly what GitLab sends — or fire realistic, correctly signed sample payloads at your own handler without touching a production account.

Start free:

No credit card · 50 requests/day free · or get a guest URL without an account

Prefer a walkthrough? Read the local webhook testing guide.

How to test GitLab webhooks

1
Create a webhook endpoint
Sign in free with GitHub or Google to create a persistent endpoint — or grab an instant guest URL at webhooks.cc/go without an account.
2
Point GitLab at your URL
Paste the endpoint URL into GitLab: Project → Settings → Webhooks.
3
Inspect what arrives
Each delivery appears live in the dashboard with method, headers, body, query parameters, and source IP.
4
Forward to localhost or assert in CI
Run whk tunnel <port> to forward webhooks to a local server, or use the TypeScript SDK to wait for and assert on deliveries in tests.

GitLab webhook signature

Signature header	x-gitlab-token
Algorithm	Shared token comparison
Verification in webhooks.cc	Supported — add your secret token and every request is checked automatically

New to signature verification? Read the webhook signature verification guide.

Send sample GitLab events

These GitLab templates ship with realistic payloads and valid signature headers. Send them from the dashboard's Send button, the SDK, or your AI agent via MCP.

pushmerge_request

# Send a signed GitLab sample with the SDK
await client.endpoints.sendTemplate( slug, {
  provider: "gitlab",
  template: "push",
  secret: "your-test-secret",
});

Everything in one place

Live dashboard — see deliveries the moment they arrive
Forward to localhost with whk tunnel
Replay any captured request to any URL
Mock responses with custom status, headers, and body
TypeScript SDK assertions for CI
MCP server for AI coding agents

GitLab webhook questions

Your GitLab webhook URL is seconds away

No credit card · or try without an account

Test GitLab webhooks

How to test GitLab webhooks

Create a webhook endpoint

Point GitLab at your URL

Inspect what arrives

Forward to localhost or assert in CI

GitLab webhook signature

Send sample GitLab events

Everything in one place

GitLab webhook questions

More providers

GitHub webhooks

Vercel webhooks

Mux webhooks

Your GitLab webhook URL is seconds away