Use case · Webhook payloads

Inspect webhook payloads

Paste a Stripe, GitHub, or Shopify webhook body and read it as a clean collapsible tree instead of a wall of escaped text.

1,000 free AI credits on signup · Core tools run locally

A webhook body arrives as one long line of escaped JSON in your logs, and you can't read it that way. Paste the raw payload here, format it, and browse the result as a collapsible tree, with each type in its own colour and the nesting laid out. When a provider field is unfamiliar, flatten the payload to dot-notation or run AI Explain to find out what it means. Want to try before you paste your own? Load a real sample: /editor?sample=stripe-webhook, /editor?sample=github-api, or /editor?sample=shopify-order.

How to inspect a webhook payload

  1. 1

    Grab the raw body

    Copy the payload from your application logs, your provider dashboard, or a delivery you replayed from the webhook history.

  2. 2

    Paste it or load a sample

    Paste the raw body into the editor. To see how it works first, open /editor?sample=stripe-webhook, /editor?sample=github-api, or /editor?sample=shopify-order.

  3. 3

    Format and browse the tree

    Format the JSON, then collapse and expand nodes to walk the structure. Strings, numbers, booleans, and nulls each get their own colour.

  4. 4

    Flatten or explain when stuck

    Flatten nested objects to dot-notation paths you can copy, or run AI Explain on a field you do not recognise to get its type and purpose.

What you get

Type-coloured tree

Every node is collapsible and colour-coded by type, so a 400-line payload becomes readable.

Mind map of the nesting

Turn deeply nested objects into a mind map and see how the parent event links to its data.

Flatten to dot-notation

Convert nested payloads to flat data.object.amount style paths you can paste straight into code or a jq filter.

AI explain for odd fields

Stripe, GitHub, and Shopify each name things differently. Run Explain on a field to get its meaning instead of digging through docs.

Runs in your browser

Formatting, the tree view, and the mind map run locally. The payload never leaves your machine unless you run an AI Copilot action.

Frequently asked questions

Which webhook providers does this work with?

Any of them. The viewer treats the payload as plain JSON, so Stripe, GitHub, Shopify, Slack, GitLab, or your own internal webhooks all work the same way.

Where can I find sample webhook payloads?

Provider dashboards show real deliveries: Stripe lists full event bodies in its Events view, GitHub has a Recent Deliveries tab on each webhook in repository settings, and Shopify logs deliveries for the webhooks you register. Provider docs also publish example payloads for every event type. To try the viewer without setting anything up, load the built-in samples at /editor?sample=stripe-webhook, /editor?sample=github-api, or /editor?sample=shopify-order.

Is the payload uploaded anywhere?

No. Formatting, the tree view, and the mind map all run in your browser. The payload is only sent to our servers if you run an AI Copilot action like Explain, which requires sign-in.

Can I share a payload via a URL?

You can share the built-in sample deep-links such as /editor?sample=stripe-webhook. Arbitrary payloads are not encoded in the URL, since the data stays local in your browser.

Is it free?

The tree view and mind map are free and run locally. The AI Copilot actions (Explain, Flatten, Generate Schema) use credits, priced by the size of your JSON, so you only pay for what each run uses. New accounts get 1,000 free credits to start.

Related tools

Read your next webhook payload

Open the Editor