How to inspect webhook payloads in an interactive json tree
- Step 1Capture a real webhook payload — Use the platform's test event delivery (Stripe Dashboard →’ Webhooks →’ Send test event) or webhook.site to capture a real delivery. Copy the full JSON body.
- Step 2Load into the tree viewer — Paste the webhook JSON. The tree shows the top-level envelope — type, data, created, id — and the nested data.object where most webhook-specific fields live.
- Step 3Navigate to the fields your handler needs — Expand data.object to explore the event-specific payload. Find and copy the paths to the fields your handler processes: customer ID, payment amount, line items, resource IDs.
- Step 4Translate paths to handler code — Use the copied paths in your handler: const customerId = payload.data.object.customer; const amount = payload.data.object.amount_received; const status = payload.data.object.status.
Frequently asked questions
How do I find the event type field in a Stripe webhook payload?+
The Stripe event type is at the top level: payload.type (e.g. 'payment_intent.succeeded'). In the tree viewer, the type field is visible as a direct child of the root node. The actual payment intent data is nested at payload.data.object.
How do Shopify webhook payloads differ from Stripe payloads structurally?+
Shopify webhook payloads do not have a data.object wrapper — the resource data is directly at the root level. A Shopify order webhook is { id: ..., email: ..., line_items: [...] } with no envelope. In the tree viewer, all order fields are top-level nodes.
Is the webhook payload data transmitted to JAD Apps?+
No. Tree rendering runs entirely in your browser. Webhook payloads with payment data and customer information are never transmitted to JAD Apps servers.
Privacy first
Conversion runs locally in your browser. No file is uploaded — only metadata counters are saved for signed-in dashboard stats.