Open Inspector
Documentation

Everything you need to inspect with confidence.

Generate endpoints, send requests, inspect payloads, and replay failures — all in one workspace.

Introduction

Live API Inspector generates a unique webhook endpoint for you. Any HTTP request sent to that URL is captured, parsed, and streamed to your browser in real-time — no refresh, no polling.

It's designed for the moment when a third-party webhook fires and you need to see exactly what arrived: headers, query, body, and metadata.

No account required. Generate an endpoint and start sending requests in seconds.

Quickstart

Three steps to your first inspected request.

1

Generate an endpoint

Create a unique URL. Every request sent to it is captured automatically.

http
POST https://inspect.dev/api/v1/inspect/generate
Content-Type: application/json

{ "name": "my-webhook" }
2

Send a request

Point any webhook provider, curl command, or your own code at the endpoint.

bash
curl -X POST https://inspect.dev/api/v1/inspect/demo-8x91 \
  -H "Content-Type: application/json" \
  -d '{"event":"payment.completed","amount":4999}'
3

Watch it arrive

The request appears in your workspace instantly. Click it to inspect headers, body, query, and metadata.

Endpoints

Each inspector has a unique slug. The endpoint URL always follows this pattern:

http
https://inspect.dev/api/v1/inspect/{slug}

Regenerating

You can regenerate the slug at any time. Old URLs stop accepting requests immediately — you'll need to update any senders.

Inspecting requests

Every captured request exposes the same structure, regardless of method:

json
{
  "id": "req_8x92a",
  "method": "POST",
  "path": "/api/webhooks/github",
  "status": 200,
  "timestamp": "2026-03-04T11:22:10Z",
  "headers": { "content-type": "application/json" },
  "query": {},
  "body": { "event": "payment.completed" },
  "ip": "140.82.115.42"
}

The JSON viewer supports collapse/expand, syntax highlighting, and formatted/raw toggle.

Replay

Send any captured request to another destination. Useful for re-triggering a failing webhook against a fixed handler.

http
POST /api/v1/replay
{
  "requestId": "req_8x92a",
  "target": "https://your-app.com/webhooks/receive",
  "method": "POST"
}
Safety note. Replay forwards the original headers and body. Remove any auth headers if the target doesn't expect them.

Webhook signatures

If you configured a signing secret, every request includes an x-signature header:

http
x-signature: sha256=8f3a7c2e1b09d4e5...

Verify by computing HMAC-SHA256 over the raw body using your secret, and comparing against the signature value.

Error handling

Common error codes and their meaning:

404Endpoint not foundSlug doesn't exist or was regenerated
413Payload too largeBody exceeds 2 MB
429Rate limitedToo many requests in a short window
500Internal errorContact support with the request ID

Ready to try it?

Generate your first endpoint — no signup required.

Create free endpoint