ShellYard

Webhook Receiver

Local HTTP listener that captures inbound requests in real time. Optional LAN-bind so vendor / device callbacks from another machine can reach it. 200-capture buffer with 1 MiB body cap. Pro and above.

The outbound REST client is half the picture. Webhook Receiver is the other half — a local HTTP listener that captures inbound requests so you can see exactly what a vendor or device is sending when their docs and the actual payload disagree.

Available on Pro and above.

Listener

  • Bind address — defaults to 127.0.0.1 (loopback only, safe by default). Flip to 0.0.0.0 to bind on the LAN so a switch, an IoT panel, or any webhook source on another machine can reach you across your local network.
  • Port — pick or autoselect. ShellYard offers an unused port from the ephemeral range.
  • Path — listen on /* to catch every request, or restrict to a single path (/hook, /events) when you’re only interested in one.

Start the listener and the URL you’d hand to the source appears in the header, ready to copy.

Capture buffer

Each request is captured into a rolling buffer of 200 most recent requests. Each capture stores:

  • Method (GET / POST / PUT / PATCH / DELETE / …)
  • Full URL with query string
  • Every header
  • Body, up to 1 MiB (oversized bodies are truncated with a marker so you still see what was sent)
  • Source IP
  • Timestamp + receive duration

Click a row to expand it; full headers and body render with the same pretty-printer the HTTP response viewer uses (JSON, XML, HTML, form-urlencoded).

Why this matters

Three common cases:

  1. Vendor docs say one thing, the payload is different. Capture the real request, compare against the docs, write the ticket with evidence.
  2. A device or switch callback isn’t firing. Bind the listener on the LAN, point the device at your machine, watch the request (or the lack of one) arrive.
  3. Building integration code. Use the captured payload as a fixture — copy it into a test, paste it into the outbound HTTP client to replay it, attach it to Magellan to help draft the parser.

Attach to Magellan

Any captured request can be sent to Magellan as context with one click. Useful when the payload is a wall of nested JSON and you want a fast “what is this trying to tell me” pass.

Tier behavior

Webhook Receiver is Pro and above. The listener and capture buffer are local to the running app; nothing about the captured requests leaves your machine unless you explicitly attach to Magellan or save into a document.