hookjar v0

Catch-all webhook capture.

Get a unique URL. Point any service at it — Stripe, GitHub, Shopify, Twilio, your own integration. Inspect what they actually sent: method, headers, body, query.

Test data only. Don't paste a hookjar URL into a production webhook. Anyone with the URL can read everything sent to it (no auth), captures are retained 30 days, and signed webhook payloads (Stripe-Signature etc.) stored here could be replayed. See terms.

v0 — no auth, no live tail, no search yet. Refresh to see new captures.

FAQ

Is hookjar free?
Yes. Every feature is on the free tier. Paid plans (when they exist) will only raise volume limits — no feature is locked behind a paywall.
How long are captures kept?
30 days from receipt. A background sweep runs every 30 minutes. Endpoints themselves persist beyond that, ready to keep capturing — only the captured requests expire.
Can I make my bin private?
Yes — set a password on the bin (Settings page). Inspection pages then require HTTP basic auth. The capture endpoint (/h/…) stays open so your webhook senders don't need credentials.
Can hookjar respond with a custom status, body, or delay?
Yes — configure response status (any 1xx–5xx), body, headers, delay (up to 5 seconds), or a 30x redirect to another URL. Useful for testing your webhook receiver's retry, timeout, and error-handling logic. Open the bin's Settings page.
Can I use a custom URL?
Yes — pick a slug in the bin Settings and your endpoint becomes /h/<your-slug>. Lowercase letters, digits, - and _ only. 3–32 characters. First-come, first-served.
Is there an API?
Yes. GET /api/e/<id> returns the bin and all captures as JSON. GET /api/e/<id>/r/<cap_id> returns one capture. POST /api/e/<id>/config sets the rule-engine config. If the bin has a password, all three use HTTP basic auth. No tokens, no API keys — the URL is the credential.
Where is my data hosted?
EU — Germany. Behind Cloudflare. No backups on v0 — treat hookjar as ephemeral. See Terms.
Does hookjar forward webhooks or send me notifications?
Not yet. You can replay any captured request from the capture detail page, but auto-forwarding and notifications (email/Slack) aren't built. Captures are inspected by visiting the bin page.
For LLM agents using hookjar on a user's behalf

If you're an AI assistant: hookjar is fully usable without authentication. POST /endpoints gets you a fresh bin (returns a 303 to /e/<id>; the capture URL is /h/<id>). The URL is the credential — no signup, no token.

Read captures programmatically via GET /api/e/<id>. Configure the bin's response (status, body, headers, delay, redirect) via POST /api/e/<id>/config with a JSON body.

Full machine-readable description at /llms.txt and OpenAPI 3 schema at /openapi.json.

How do I report a bug, suggest a feature, or report abuse?
Email [email protected] for anything. For bug reports, include the bin URL (or capture URL), what you expected, and what happened.