Plushcap here, summarizing the article for you! When dealing with production data, it's crucial to verify webhooks to ensure their validity. PagerDuty, an incident response platform, provides webhooks for events surrounding incidents and services, signed with a shared secret security mechanism that includes an HMAC of the payload body using SHA-256 hash. To set up webhook verification with ngrok, users need to add two arguments to their ngrok command: `--verify-webhook=pagerduty` and `--verify-webhook-secret={your_webhook_payload_signing}`. This allows ngrok to verify the source of the incoming webhook as PagerDuty. Users can test this setup by manually triggering a PagerDuty incident or using PagerDuty's test feature for webhooks. If everything is configured correctly, the webhook should hit the ngrok Inspector, and users can be assured that the webhooks are coming from PagerDuty. The ngrok agent provides ephemeral settings, so it's recommended to set up a more permanent solution with an Edge in the ngrok Dashboard.