---
title: "Vercel Webhook Tester — Test & Inspect Online | WebhookRelay"
meta:
  "og:description": "Test and inspect Vercel webhooks online with a free webhook tester URL — capture real Vercel payloads, read the signature header, then forward locally."
  "og:title": "Vercel Webhook Tester — Test & Inspect Online"
  description: "Test and inspect Vercel webhooks online with a free webhook tester URL — capture real Vercel payloads, read the signature header, then forward locally."
---

![Stripes](https://webhookrelay.com/blog/vercel-webhook-tester/images/stripes.svg)

# **Vercel Webhook Tester — Test & Inspect Online**

Test and inspect Vercel webhooks online with a free webhook tester URL — capture real Vercel payloads, read the signature header, then forward locally.

![Vercel Webhook Tester](https://webhookrelay.com/blog/vercel-webhook-tester/images/blog/heroes/tester.jpg)

If you are wiring up Vercel webhooks, the first question is always the same: _what does Vercel actually send?_ The docs show an idealised payload, but the real request — its headers, its `x-vercel-signature` header, the exact JSON shape — is what your handler has to parse. A **Vercel webhook tester** gives you a public URL that captures those real requests so you can read every byte before you write any code.

## [Get a free Vercel webhook tester URL](#get-a-free-vercel-webhook-tester-url)

The fastest way is our free [Webhook Bin](https://webhookrelay.com/blog/vercel-webhook-tester/webhook-bin/) — a no-code [webhook tester](https://webhookrelay.com/blog/vercel-webhook-tester/webhook-bin/) that gives you an instant public URL and stores every request that hits it, headers and body included. No signup, no deploy:

1. Open the [Webhook Bin](https://webhookrelay.com/blog/vercel-webhook-tester/webhook-bin/) and copy the URL it generates for you.
2. In **your Team or integration settings → Webhooks in the Vercel dashboard**, add a webhook endpoint and paste that URL.
3. Trigger an event (see below) and watch the request land in the bin in real time.

Because the bin keeps the full request, you can inspect the `x-vercel-signature` header, the `Content-Type`, and the complete payload — the three things you need to build and verify a handler.

## [What a Vercel webhook looks like](#what-a-vercel-webhook-looks-like)

Vercel delivers webhooks as an HTTP POST with a `application/json` body. Vercel signs the raw body and also sends the event type in the payload's `type` field — capture both so you can route on the event and verify the `x-vercel-signature` digest.

A typical `deployment.created` payload looks like this:

```
{
  "id": "evt_...",
  "type": "deployment.succeeded",
  "createdAt": 1700000000000,
  "payload": {
    "deployment": {
      "id": "dpl_...",
      "url": "my-app.vercel.app",
      "state": "READY"
    },
    "project": {
      "id": "prj_..."
    }
  }
}
```

Common Vercel events you will want to test:

- `deployment.created`
- `deployment.succeeded`
- `deployment.error`
- `project.created`

## [Verifying the Vercel signature](#verifying-the-vercel-signature)

Vercel signs each request so you can prove it really came from Vercel. The signature travels in the **`x-vercel-signature`** header and is HMAC-SHA1 of the raw request body, using your integration's client secret. Capture a real request first, then use our [HMAC signature verifier](https://webhookrelay.com/blog/vercel-webhook-tester/hmac-verification/) and the [verify a webhook signature](https://webhookrelay.com/blog/vercel-webhook-tester/blog/verify-webhook-signature/) guide to confirm your verification logic against a payload you can actually see.

## [From inspecting to receiving on localhost](#from-inspecting-to-receiving-on-localhost)

A bin is perfect for _seeing_ the payload. When you are ready to drive your **local** handler with real Vercel events — without deploying — forward them straight to `localhost` with the Webhook Relay agent. The full walkthrough is here: [Receive Vercel webhooks on localhost](https://webhookrelay.com/blog/vercel-webhook-tester/blog/receive-vercel-webhooks-locally/).

That gives you a stable public URL that tunnels to your machine, so Vercel keeps delivering to the same endpoint while you iterate on `localhost`, no firewall changes or public IP required.

## [Test Vercel webhooks online in three steps](#test-vercel-webhooks-online-in-three-steps)

1. **Capture** — point Vercel at a [Webhook Bin](https://webhookrelay.com/blog/vercel-webhook-tester/webhook-bin/) URL and inspect the real request.
2. **Verify** — confirm the `x-vercel-signature` header with the [HMAC verifier](https://webhookrelay.com/blog/vercel-webhook-tester/hmac-verification/).
3. **Forward** — when the shape is clear, [receive Vercel webhooks on localhost](https://webhookrelay.com/blog/vercel-webhook-tester/blog/receive-vercel-webhooks-locally/) and build your handler.

New to webhooks in general? Start with [what is a webhook](https://webhookrelay.com/blog/vercel-webhook-tester/blog/what-is-webhook/) and [how to test webhooks](https://webhookrelay.com/blog/vercel-webhook-tester/blog/how-to-test-webhooks/).

Ready to inspect your first Vercel event? [Open a free Webhook Bin](https://webhookrelay.com/blog/vercel-webhook-tester/webhook-bin/) and paste the URL into Vercel.