Skip to main content

Documentation Index

Fetch the complete documentation index at: https://supahooks.ar27111994.dev/llms.txt

Use this file to discover all available pages before exploring further.

Webhook Debugger & Logger runs in two modes: on the Apify platform, where you get a public webhook URL within seconds, or self-hosted via Node.js or Docker for environments where you control the infrastructure. Choose the path that fits your workflow.

Run on Apify

The Apify platform is the fastest way to get a live webhook endpoint. No installation, no port forwarding — Apify handles the public URL and storage for you.
1

Open the actor in the Apify Store

Go to apify.com/ar27111994/webhook-debugger-logger and click Try for free.
2

Configure your input

Set your preferred options in the input form. A minimal configuration to get started:
{
  "urlCount": 3,
  "retentionHours": 24,
  "enableJSONParsing": true,
  "maskSensitiveData": true
}
See Input reference for all available options.
3

Start the actor

Click Start. The actor generates your webhook endpoints immediately and exposes them through the Apify web server URL.
4

Find your webhook URLs

Once the actor is running, open the web server URL and call /info to retrieve your active webhook endpoints and the full API surface.
Keep the actor warm with Apify Standby mode so your webhook endpoints stay ready for incoming traffic without paying a cold-start penalty on each request. This is especially useful for long-running debug sessions or when you need the endpoint available on demand.

Environment configuration

These are the key environment variables for both Node.js and Docker deployments.
VariablePurposeDefault
ACTOR_WEB_SERVER_PORTHTTP port the server listens on8080
INPUTFull actor input as a JSON string — sets urlCount, retentionHours, authKey, and all other optionsunset
APIFY_LOCAL_STORAGE_DIRDirectory for captured events, webhook state, and large payload offloads./storage
LOG_LEVELLogging verbosity (info, debug, warn, error)info
For the full list of environment variables and advanced tuning options, see Environment variables.
Generated webhook URLs are public unless you set authKey, allowedIps, or signatureVerification in your input. Do not point sensitive production traffic at unsecured endpoints.