Quick Start Guide

Get Started in 60 Seconds

HookLab gives you instant webhook URLs that capture every incoming request. Inspect headers, bodies, and metadata — then replay webhooks to your server whenever you're ready.

1. Create a Webhook Endpoint

curl -X POST https://hooklab-webhook-testing-and-debugging.p.rapidapi.com/api/v1/endpoints \
  -H "Content-Type: application/json" \
  -H "X-RapidAPI-Key: YOUR_KEY" \
  -H "X-RapidAPI-Host: hooklab-webhook-testing-and-debugging.p.rapidapi.com" \
  -d '{"name": "my-webhook"}'

2. Point Your Webhook Provider at It

Copy the url from the response and paste it into your webhook provider's settings (Stripe, GitHub, Shopify, Twilio, etc). Any HTTP method works.

3. Inspect Captured Requests

curl https://hooklab-webhook-testing-and-debugging.p.rapidapi.com/api/v1/endpoints/{id}/requests \
  -H "X-RapidAPI-Key: YOUR_KEY" \
  -H "X-RapidAPI-Host: hooklab-webhook-testing-and-debugging.p.rapidapi.com"

You get back every captured webhook with full details: method, headers, body, query params, IP address, and timestamp.

4. Replay to Your Server

curl -X POST https://hooklab-webhook-testing-and-debugging.p.rapidapi.com/api/v1/replay \
  -H "Content-Type: application/json" \
  -H "X-RapidAPI-Key: YOUR_KEY" \
  -H "X-RapidAPI-Host: hooklab-webhook-testing-and-debugging.p.rapidapi.com" \
  -d '{"request_id": "req_abc123", "target_url": "http://localhost:3000/api/webhooks"}'

Same headers, body, and method — sent straight to your server. Fix a bug? Replay again. No waiting for retries.

Common Use Cases

Testing Stripe webhooks locally — Point Stripe at your HookLab endpoint, make a test payment, inspect the exact payload, replay to your local server.

Debugging GitHub webhooks — Capture push/PR events, see the full payload, replay to test your CI/CD handler without real commits.

Shopify integration development — Capture order and inventory webhooks. Shopify trials expire, but your captured payloads stay for replaying anytime.

Comparing webhook payloads — When a handler breaks in production, capture the failing payload and inspect exactly what was sent vs what your code expected.

Endpoint Reference

Endpoints (Webhook URLs)

Method	Path	Description
POST	/api/v1/endpoints	Create a new webhook endpoint
GET	/api/v1/endpoints	List all your endpoints
GET	/api/v1/endpoints/{id}	Get a specific endpoint
PATCH	/api/v1/endpoints/{id}	Update endpoint settings
DELETE	/api/v1/endpoints/{id}	Delete an endpoint

Webhook Capture (Public — no auth needed)

Method	Path	Description
ANY	/hook/{endpointId}	Capture any incoming webhook (give this URL to Stripe/GitHub/etc)

Captured Requests

Method	Path	Description
GET	/api/v1/endpoints/{id}/requests	List captured requests
GET	/api/v1/endpoints/{id}/requests/{requestId}	Get full details of a captured request
DELETE	/api/v1/endpoints/{id}/requests/{requestId}	Delete a captured request
DELETE	/api/v1/endpoints/{id}/requests	Clear all captured requests

Replay

Method	Path	Description
POST	/api/v1/replay	Replay a captured request to a target URL

Utility

Method	Path	Description
GET	/health	Health check
GET	/api/v1/auth/usage	Check your usage stats

Plan Limits

Feature	Basic (Free)	Pro ($19/mo)	Ultra ($49/mo)
API calls/day	100	5,000	50,000
Active endpoints	3	25	100
Request retention	24 hours	7 days	30 days
Max body size	64 KB	256 KB	1 MB
Replays/day	10	500	5,000

Response Format

Every response follows the same format:

Success:

{
  "status": "success",
  "data": { ... },
  "meta": {
    "request_id": "req_V1StGXR8_Z5j",
    "timestamp": "2026-02-08T10:30:00Z"
  }
}

Error:

{
  "status": "error",
  "error": {
    "code": "ENDPOINT_NOT_FOUND",
    "message": "Endpoint not found"
  },
  "meta": {
    "request_id": "req_V1StGXR8_Z5j",
    "timestamp": "2026-02-08T10:30:00Z"
  }
}

Rate Limiting

Every response includes rate limit headers:

X-RateLimit-Limit: 100
X-RateLimit-Remaining: 87
X-RateLimit-Reset: 1707400000

When you exceed your limit, you'll get a 429 Too Many Requests response with a Retry-After header.

Need Help?

Check your usage stats at GET /api/v1/auth/usage to see if you've hit a limit. For bugs or feature requests, use the "Contact Provider" button on this page.