Skip to content

Receiving Webhook Requests

Once you have an endpoint URL, any HTTP request sent to it is automatically captured and displayed in your dashboard.

How It Works

Third-party Service (e.g. Stripe)
│ POST /h/{endpoint-id}
HookNexus API
├─► Store in D1 database
└─► Push via WebSocket → Dashboard (and Plus API Key clients)
  1. A third-party service sends an HTTP request to your endpoint URL.
  2. HookNexus captures the full request (method, headers, body, query params).
  3. The request is stored in the database.
  4. A WebSocket message is pushed to all connected clients.
  5. The request appears in your dashboard instantly.

Supported HTTP Methods

HookNexus accepts all standard HTTP methods:

MethodSupported
GET
POST
PUT
PATCH
DELETE
HEAD

Supported Content Types

Content TypeParsingDisplay
application/jsonParsed as JSONSyntax-highlighted JSON
application/xmlParsed as XMLSyntax-highlighted XML
application/x-www-form-urlencodedKey-value pairsTable view
multipart/form-dataForm fields extractedTable view
text/plainRaw textPlain text
OtherRaw bytesHex/raw display

Configuring Third-party Services

Point any webhook-capable service at your HookNexus URL.

In Stripe Dashboard → Developers → Webhooks → Add endpoint:

https://api.hooknexus.com/h/YOUR_ENDPOINT_ID

Select the events you want to receive (e.g., checkout.session.completed).

Viewing Request Details

Click on any request in the list to see full details:

  • Headers — All HTTP headers in a key-value table
  • Query Parameters — Parsed from the URL query string
  • Body — Formatted with syntax highlighting (JSON, XML, etc.)
  • Metadata — IP address, content size, timestamp

Request Size Limits

PlanMax body (typical)
Free64 KB
Plus512 KB

Requests exceeding the limit receive 413 Payload Too Large.

Log Retention

PlanUser-visible retention (typical)
Free24 hours
Plus30 days

After the retention window, requests no longer appear in the dashboard. On Plus, use log export if you need to keep copies outside HookNexus.