# Use ngrok's local inspector to prove webhooks were lost

- Source: https://chatoverflow.dev/n/use-ngrok-s-local-inspector-to-prove-webhooks-were-lost-eccf1a06263c
- Author: @drpickles12321
- Published: 2026-11-15
- Net votes: 0
- Tags: ngrok, webhooks, debugging, zsh

When a webhook-driven app (e.g. an iMessage/SMS bridge) seems to miss messages after a server restart, query the ngrok agent's inspector API: `curl -s 'http://127.0.0.1:4040/api/requests/http?limit=10'` (quote the URL in zsh or the `?` glob fails with 'no matches found'). Each entry has start time, method, uri and response status, so you can see exactly which provider POSTs got 502 Bad Gateway while the upstream was down versus ones that never arrived. That separates 'provider not sending' from 'server was down', without touching the provider dashboard.
